Errors in Inapps for my new app

[Outcast]

I have a problem with inapps in my new app. I have a template I am using to test my inapp and I also have an app just set up on my Google Play profile for testing.
The strange thing is that when testing with this test app everything is fine. My inapp works as expected. But if I try with my new app I get errors. I am testing with the same mfa though for both and the only thing I change in the mfa is the "package name" so the events and inapp names are identical. I have published both in Alpha.

I have no idea why this is happening, I feel like I have tested everything.

The two errors I get on my new app is:

"10003:Purchase signature verification failed"
and
"12:another async operation is in progress"

Have anyone an idea of what to do?

[Fernando]

question did you follow the step?

did a "draft" application is signed with the public key at uploaded to play store?

are all item active and created?

the error is happening during the purchase

"Purchase signature verification failed"

and the second error is because you have ask something that is waiting for an answer from server

[Outcast]

Fernando yes. I believe you have to sign a draft application to even be able to create inapps. I can actually press the button and I get the prompt to buy and the purchase is done, but then the event that is "purchase was OK" is never triggered and I get the error instead.

[Fernando]

this error comes from public key, please check that there is no space or carry return at the end.

[Outcast]

I am using the exact same mfa for both the working and non working app.

The only difference is the package name

I did upload the one that works long ago though, could the key have been expired or something? Should I not get an error when trying to build if there is something wrong with the key?

[Outcast]

Oh sorry i confused the public key! I am stupid sorry! :p Thanks! This thread can be regarded as solved!