There was such a problem. Users are upgraded to Windows Phone 8.1 and eventually they disappear internal purchases. This is repeateŠ² for not all users.
That is situation that a user makes a purchase on WP8 within an application and enjoys paid functionality. Updated on WP8.1 - internal purcahse disappears. I note that in the code there is a check in the store on the availability of purchase.
The same behavior if the user to reset the phone to factory settings - internal purchases disappear.
Nobody faced with such a problem?
Related
I have a paid app and I would like to give some users free access.
I have no in-app purchases and the Features tab in App Store Connect says "Promo Codes can only be generated for approved versions".
How do I generate a promo code?
Provided you have a released version of your app it should be listed in the Features tab, the message you are seeing suggests your app is not yet approved and available for purchase. Just wait until it is. HTH
Edit: The link in your question did not work for me so I assumed the app was not approved. However I just found it by searching the App Store. It has only just been released, the Features tab is probably lagging a bit, as before just wait a while and it should appear.
On this bug report on Github https://github.com/googlesamples/android-play-billing/issues/2#issuecomment-305380836 we were asked to raise the issue here.
The issue is simple. The user has 2 or more accounts on their phone, let's say xyz#gmail.com and abc#gmail.com. They install an app with the account xyz#gmail.com. They purchase some IAP items. The app updates and now the app is under abc#gmail.com and the user has lost the purchase. This happens a lot when using staged rollouts.
The main issue, as developers we aren't allowed to let the user choose which account to buy with or which account to check for purchases with.
The second issue, the Play Store app on Android ignores the user account selected on the hamburger menu. The only workaround for this is to use the Play Store website as described in this workaround https://github.com/googlesamples/android-play-billing/issues/2#issuecomment-259108286 on the same bug report.
I don't know what the ideal solution is, all I know is that this is a huge hassle for developers leading to a lot of 1-star reviews after each update.
EDIT: As pointed out in a comment, when I refer to multiple accounts I am talking about multiple Google accounts for a single Android User, I am not talking about multiple Android users within the same phone.
When I try to deploy my XAP to the Windows Phone, I get the "error 0x89731812" message.
Your device has a locked screen. Unfortunately, this is not documented anywhere, but there is a discussion with some hints on page 3.
Turn on your phone (if it isn't already)
Slide open
Type your password to unlock
Retry the deployment after unlocking your screen.
EDIT: My bad (well, that of my search engine). They are documented here. Thanks keyboardP!
As I Stumbled upon this old thread I might have found a solution for this Error code.
I've had the same message as I found out that my device wasn't recognised properly in device manager.
Did some research and saw that the driver wasn't picking the right USB-port as it was registered to one of the other usb ports.
After inserting the Phone to the first USB port where it was registered the Initial first time everything went ok!
If your phone charge is very low, it won't deploy the app too.
To deploy you must:
1.Connect your wp7 phone
2.Open Zune
3.Open the deployer
4.unlock your phone (As said before)
5.Deploy
It requires an unlocked phone (without restrictions) or an Interop Unlocked Phone, and the phone mustn't have low charge.
I just downloaded the Beta sdk for admob on WP7 and after including the banner in the app(and viewing the default banner in the emulator mode) i've added the admob on-site publisher id an tried to run the app on a real device but there was no add showed (in debug and in release mode). The space is reserved (~75px of black space).
When looking in the console i see "Error - Ad Not Available (NoFill)" and on the admob site i see that there wasn't no ad request ever made. I got to the following conclusions:
1) there are no ads for my app due to windows phone's still-limited presence (but why isn't my app showing ad requests on admob site?). Also i found this on google's site :
Windows Phone 7 is new to the AdMob market, so in the short term you
may see some low fill rates until advertisers add this platform to
their targeting. Using test mode during development should eliminate
inventory as a variable in your SDK integration testing.
2)i've just created my admob ad so maybe google has a certain approval process.
Any other ideas of this problem? Has anyone else experinced it, and if so, how did they get over it?
UPDATE my app is now active on the adMob site and can see requests (122) , a fill rate(3.28%), eCPM(0), RPM(0) but the ads are still not showing. What can be the issue?
How would I go about adding a trial version and achievements for my Windows Phone 7 game?
And how can I make the game upon finding it's a trial prompt the user to purchase the game and redirect him/her to the games page on the AppHub?
For a trial version you can use the IsTrial API call - information about it on MSDN - you call this once in your game and assign a TrialMode value in your game to it as checking this in a Game Loop is not recommended, then you can have logic in your game change depending on what this value is - the Marketplace process takes care of the process of Try & Buy once you mark your app during the submission process as having a Trial mode.
Achievements are only available for Xbox LIVE enabled games which requires a special publishing relationship with Microsoft, I'm not sure of the process but try the create.msdn.com App Hub website, there may be information there, this is not open for all developers, as even now there are very few Xbox LIVE enabled titles in Marketplace