I'm building an app that include in app purchase (subscription based): the user is required a subscription to consult more that X time a given section of the app per week, however i'm facing a problem as the user can bypass the limitation by changing the time of his iPhone.
I know that one solution would be to verify the time on a server side, but the app is to run without internet connexion...
S how can i get the REAL device time (NOT THE USER DEFINED TIME).
thanks.
Related
I have a problem with the YouTube Livestreaming API, and it is only causing a problem on one single account.
The CMS I support has a live to YouTube function that automatically schedules and delivers a livestream from our studios to YouTube as a parallel channel to our website. We support multiple teams who all authenticate their accounts against our application to do this.
About 6 weeks ago we had a single group report that they are no longer seeing their content streaming live to YouTube. All the other accounts, as well as our test channels, are working fine.
With the account in question we can see the livestream get created, the broadcast is created, and they are bound together. Once the encoders are started we are able to successfully transition the stream to "TESTING" without problem approximately 10 minutes prior to the scheduled start time. Where we are seeing the problem is in the final step where we transition the stream from "TESTING" to "LIVE" at the starting time of the broadcast. We get a response with "(#100) Status transition not allowed" when we attempt to transition to live. Prior to this step we retrieve the lifeCycleStatus value, and it shows as "TESTING".
If a user logs into YouTube Studio at this point, they are able to manually transition the stream to live.
The fact that this is working with multiple other accounts, and all are using a common code base and app, I am concerned that there is something about the account itself that is causing this issue. I have not been able to see any significant differences in the account settings when comparing with our test account.
Is there any way I can get further information about why the transition is failing, or something I should be specifically looking for as a potential problem?
I have an application listed via Fabric. The stability alert email shows Crash-Free Users has dropped to 66.4%. for one day but if I observe the same in Fabric for that day, it shows a different value. How is this being calculated since it is making us think if the application is really causing the issue or the statistics being reported are incorrect? Image showing the Crash Free Users for that day below :
I need a bit of guidance, so for my application i'm looking at using local notifications to send a notification every morning at 7 o'clock.
The issue i'm having is how can i make the content for the local notification dynamic mainly the body and the attached image? As it will vary for the user on a daily basis.
What would be the best way to go about this since you can't edit future notifications.
Here's a little lesson about notifications. First, what is a notification? It's basically an alert presented on your behalf by the system. Second, there are two kinds of notification: local and remote.
Let's imagine, then, an app that aims to present a notification to the user every morning at 7 AM saying what the current temperature is outside. (Assume for purposes of the example that we have a way of learning this information.)
A moment's thought will reveal that this cannot be done with local notifications. We cannot know the current temperature at 7 AM until 7 AM (or close to it) and we cannot schedule the notification unless the app is running. Therefore we would need the great good luck to have the app running at 6:59 AM in order for this app to work. But an app only runs when the user summons it, so that is extremely unlikely.
Therefore a task of this kind is possible only with remote notifications. A remote server is always running; therefore it can get the temperature and "ping" the user's device at 7 AM, and the system will present the notification on your behalf. You would therefore need to possess such a server in order to write the imagined app.
(An alternative using local notifications would be this: You schedule, say, a week's worth of local notification in advance. Then if you have the great good luck to find the app running before a notification is presented, you tear down all the scheduled notifications and do it again with a more up-to-date forecast. But of course this cannot possibly work as well as using remote notifications, and it will stop working entirely after a week if the user doesn't launch the app. That, to put it bluntly, sounds pretty lame.)
I'm almost ready with developing my first windows phone app. Can anyone tell me how long it will take to get the app in the store. For ios apps the apps must be approved, that usually takes about a week, for Android it usually takes only a couple of hours. How is it for Windows, does Microsoft approve the app?
Second question: I need a url for the app that refers to the windows app store?
Is the url known in advance or do I have to publish first before I know the exact app store url of my app?
Thanks for the help!
First question: At this moment it is around 3 to 4 hours for a republish and a day for normal a full publication. Just submitted an app last week. These times can change, one of my (new) apps was through the publication in 1 hour. Do keep in mind that it can take some time before you see it in the stores (up to 24 hours)
Second question:
When you submit your publication you can see the url of your app.
In my app
http://apps.microsoft.com/windows/app/1rm/d8639e5b-93ae-4d34-a575-d84e205c134d
I get an error message when users press submit after rating.
Get error c101a006.
Not sure why this happens, open store but not able to submit review
As far as I can see no rating can be submitted due to error, at least not on Windows 8 machines running more than one account. How can I verify rating works now on machines running one account?
It is ZEST_E_INTERNAL_SERVER_ERROR, an error that tells you that the Store server suffered a heart-attack when trying to process the submission. The rating page itself is displayed by the Store app on your machine. I had no trouble myself submitting a rating for your app.
So this has nothing to do with your app itself. Web server errors happen, they can take a few days to get resolved. At least from my test it is clear that the server can no longer be the problem. If you still have trouble then there's something wrong with your Microsoft account. Login on this web page and double-check that your birthdate and home country have been entered.
Without any code it's difficult to say.
Anyway searching googling the error code I went to Microsoft support site That says it's a server error, for example when account data are not completed. It's hard to do more with only these informations.
My friend was getting the same error since he was from Siberia and this is how Microsoft responded to him. Its mainly caused when one tries to rate an app while the app marketplace aint supported in that region.
Go to settings > region and language > change the phones region to a supported country > restart the phone (change to UK preferably)
Go to http://support.xbox.com/en-US/billing-and-subscriptions/account-management/change-region and click on Account migration
Sign in with your xbox account (in some cases they will send you verification code on email address which you added before)
Finish account migration to UK (in my case). Please keep in mind that they allow you to do this only ONCE per 3 months
Problem solved. Try to download free apps or games and everything will work.
Solution for application which requires payments:
1. Go to settings > region and language > change the phones region to a supported country > restart the phone
2. Go on store. Find some game or application for payment.
3. Add payment option which you wish
Enjoy and cheers :)
Note 1: I suggest you to complete account migration on Xbox from other device (PC/Mac)
Note 2: Xbox region restriction was cause of this error