I can't do Inapp purchases anymore, please help :/

[Outcast]

I have a problem. I have made inapp purchases before for one of my game and it was a smooth experience with testing. Now however I cant get any test app to respond anymore to any purchase requests. Something must have happened. It was just after this happened: http://community.clickteam.com/threads/83584-Testing-inapp-just-keeping-popping-up
(I just keept getting pop ups of buy confirms for an inapp i was testing) I "solved" this problem finally by going into apple connect and removing the actual inapp that was called on. But after this I have not been able to do any inapp requests! I have tried on 3 different projects, including one I created clean just to try on. I am really at a loss as to what to do. The clean app i made just for testing I used Andos tutorial mfa and just changed the bundle identifier and the name of the inapp: https://dl.dropboxusercontent.com/u/...pPurchaset.mfa
All the info should be right:
https://dl.dropboxusercontent.com/u/...-09_185043.png
https://dl.dropboxusercontent.com/u/...-09_185103.png

I have not had a problem with this before When i do build Andos test app and run it on my device the right information is retrieved and the button appears with the name of the inapp and the price and info. But when clicking on the button nothing happens. No pop up request from apple to ask if i want to buy it pops up.
I have tested to try to initiate buys from other apps I have downloaded from the appstore and those works so I have no idea what is wrong.
I have really no idea what to do at this point Some help would be greatly appriciated.. :/

[Outcast]

Edit: No. I thought it start working but now nothing happens again.. :/

[Anders]

I believe you *have* to submit a screenshot of the item in question to Apple, even if it's just a dummy image. Apple are very strict when it comes to the setup of everything.
Can you try that and see if it works?

[Outcast]

I had this problem first with my "real" app and that one had a screenshot. Its just this test version that I have not uploaded one for, and I don't think that is necessary. In fact I did try it today and I got the pop up. But then I tried later, and now it would not respond again. It seems to have been very unstable since the thing with the infinite pop ups I described in the other thread. Now when I press the buy button it is disabled because I cant press it again, but the pop up never appears. I will try to restore my device.. see if that helps :/

[Outcast]

Hm I may have tracked down a part of the problem I think. I added a counter to the my app and I see the "request payment" event was continuously firing because a flag did not turn off in an early test verion. So that event fired like 100+ times. Now the annoying thing is that I dont know how to reset this. It seems like if you have an app and this have happened once by accident you cant get it to work normally again without creating a whole new app on Itunes Connect. I tried both removing the actual iap and to create a new bundle identifier but after this happened I cant get any response anymore when clicking the buy button. I guess the other calls are laying in waiting and blocking the new calls or something even when the app have been uninstalled?

[Outcast]

My only "solution" is to create a whole new app in Itunes Connect. Make sure this does not happen if you already have an existing app published, then I dont know if there is any way to solve it.

[mobichan]

I haven't had any issues with IAP on the Slayin update we are about to submit. Did you by chance upgrade to Fusion 2.5? I need to hold off upgrading because of potential bugs popping up now after we have done extensive testing.

[Outcast]

No I have not yet upgraded, I will do after this project though But no as long as you dont do the mistake I did of testing and forgetting to ad flag that prevents "request payment" to be sent over and over again many times you should be fine. This "bug" happened because of this, and the two apps this has happened on can no longer use any iap it seems. I created a new one though and now everything is working fine again.