subscriptions

i've got an android app with in-app subscriptions. After the user has purchased a subscription, i request the "validUntilTimestampMsec" and "initiationTimestampMsec" through our backend by the Google API. The returning timestamp "initiationTimestamp" is correct and represents the time the user has made the purchase, but the returning timestamp "validUntilTimestamp" has always a difference of +12 hours to the real valid-until time i need. The function i use to retrieve the date is simmilar to both timestamps. Where does the 12 hours come from and how can i get the correct time. The expire date

Using stripe's API with Ruby on Rails I am unable to save subscriptions. I am able to retrieve and update and save customer objects: customer = Stripe::Customer.retrieve(some_customer_id) #this works customer.save #this works I am also able to retrieve subscriptions: subscription=customer.subscriptions.retrieve("some_subscription_id") #this works However, when trying to save a subscription: subscription.save #this doesn't work I keep getting this: NoMethodError: undefined method `save' for #<Stripe::StripeObject:0x007ff37147c720> from /Users/me/.rvm/gems/ruby-2.0.0-p353/gems/stripe- 1.9.9/lib

I'm new to Azure Service Bus and have created successful pocs for creating a topic and a separate subscriber application to receive its message. Based on this article, I quote: "A topic can have up to 2,000 subscriptions associated with it, each of which gets independent copies of all messages sent to the topic. One or more subscribers can independently subscribe to a subscription and compete for messages from it." http://convective.wordpress.com/2011/06/08/windows-azure-appfabric-service-bus-queues-and-topics/ What I'm interested to do is to expand this for multiple applications to

I am finding that the renewal of an expired auto-renewing subscription is never being delivered while the application is active and running, but rather when the application is woken up from background or on launch. In other words if you are using the app, and the subscription expires, it won't be delivered to the app (assuming it is auto-renewing and valid etc) while the user continues to use the app. This behaviour does not seem to be documented by Apple, can anyone else with experience of this confirm or otherwise? Obviously one can detect that the sub has expired and then offer the user the

I ordered a auto-renew product, After 5 minutes ,it become expired! I think in Sandbox 5 minutes is equal to 1 month, At the end of current subscription peroid(after 5 minutes), it should't be auto-renewed? but it become expired. This is my experience as well. Auto-renewing in the sandbox environment is inconsistent. On some occasions I've seen a sandbox subscription auto-renew about 5 times before ending. But on other occasions it doesn't auto-renew at all. I assume these problems don't exist in the production environment. Enrico Susatyo In the sandbox environment, auto renewable

In my office, many of us use SSRS to schedule recurring reports. I want to view the schedule of upcoming report runs, for the next few days or a week, so that we can see whether 20 reports are all going to try to run at the same time. How can I accomplish that? I've created t-sql reports that show subscription information, but they only show "last run" dates and times. That's not helpful for predicting tomorrow's bottlenecks. The solution should include data-driven subscriptions too. SSRS stores all of its data in the ReportServer database so you'll need an account with read access to this

I am building an app for a client that will have 30 days of content for free, thereafter you are required to buy a subscription via in app store purchases. However, I have read that you will get rejected if you have trials. Don’t set time limits on any of the functionality of your app, either for run times or life times. Applications that only run for a set number of minutes per session, or that expire altogether after some period of time, don’t recruit customers so much as leave a bad taste in their mouths. Finally, they also say "your app will be returned to you by the App Review Team for

I am developing an application with in-app subscriptions. On our servers, I check the validity of each subscription through the Google Play Developer API . As stated in the docs, a request to the Purchases.subscriptions endpoint, returns something like that: { "kind": "androidpublisher#subscriptionPurchase", "startTimeMillis": long, "expiryTimeMillis": long, "autoRenewing": boolean } However, I am finding some strange behavior with it. When a user cancels a subscription through Google Play app, the "startTimeMillis" field is updated to the time of cancellation . According to the documentation,