I have an uploaded but not yet approved paid app. When it'll be approved I'll request a promo codes. So can people download my app via these codes before it would be realesed?
Version of app is 1.0 and it's not an update.
Sorry if my question seems nooby, but i cant' find an answer.
Thank you for answering.
Yup.
Curse you, minimum character limit!
Yup: Just make sure you set the release date at some point in the future. As long as your app is pending developer release rather than review, promo codes should work. :)
Related
Hope you're well. Two quick guidance questions from the community. And I really value your advice. We're a fintech company and hoping to do an external tester effort of a few thousand folks in testflight. That said, had two questions:
I recall it's not possible to test actual transactions in testflight (commerce, banking, otherwise). Is that the case or am I mis-remembering?
Irrespective of the above, one of the concerns is the transition from testflight to live app store. If I recall correctly, there's no way to port X number of people in your external tester effort to the live app and save their info, correct? You basically have to start fresh with those folks (i.e. have them go to the app store, download the released/consumer version, then set up all new accounts where it'd be hard to port to their new accounts their testflight account data)?
Warmest thanks for the feedback! Hope the appreciation comes across.
Evan
I'm planning on deleting my crashlytics account.
But before I do that, how do I know the previously released versions of my ios app which talks to crashlytics will continue to work (aside from the crash reporting)?
It shouldn't crash because the account was deleted right? I'm trying to find any documentations that will tell me it won't crash, but I'm not seeing any.
Thanks
Great questions, we recently shipped a docs that will help you to understand what will happen "After March 31, 2020". Her is the link to the docs. If you still have questions, please reach out us AT 'support#fabric.io'
I just started developing an Intuit App yesterday and was really getting going on integrating with QuickBooks Desktop. Then today I logged in to continue work and was greeted by several missing pages on Intuit's IPP site and a link that says "Deprecated QBO V2 and QBD V2,V3". The only API that appears to not be deprecated is QBO V3.
I cannot find any announcement from Intuit about any upcoming deprecation. Does anybody have any info on whether I am safe to continue developing my app to connect to QBD or do I need to talk to our accountant to move over to QBO instead?
EDIT: I have marked Jarred's answer as the accepted answer because he associated with Intuit and answers my specific situation. Also check Charlie's answer for additional details specific to other scenarios.
I interviewed several people from Intuit at the Sleeter Accounting Solutions Conference this week, including (amongst others) Dan Wernikoff, Senior VP.
I'll have an article in my blog on this (http://www.sleeter.com/blog/) next week - I'm transcribing my recordings and clarifying points.
There are a LOT of points here, but to address what you are looking at -
If you are writing an IPP app using V3 for QBO - no problem (and in fact, some good news there).
If you are already published with IPP using V3 and Sync Manager for the Desktop, you will get continued support but don't expect any advancement there (unless you are someone big like American Express).
If you are NOT already published with IPP for the Desktop - the SDK is your option.
And there is a lot more info about this coming out
MINOR EDIT AT A LATER DATE: If you have been working with IPP for the desktop you MIGHT get approved to continue - no guarantees on that (but it seems they might be lenient). But In my opinion you can't expect any significant new features (as in, more data access) moving forward unless you are a significant partner with a contract with them (such as, American Express).
Intuit will not prevent you from going live with your application that you have spent the last 6 months working on. We have a set of guidelines for grandfathering in developers who have invested in using the v2 REST API for QuickBooks Desktop.
feel free to contact me directly if you have more questions.
#Charlie if you could correct your statement regarding if you are NOT published then you need to use the QBXML SDK. That is too generic, we will evaluate each developer on a case by case basis.
regards,
Jarred
My writeup on this subject is available at http://www.sleeter.com/blog/2013/11/quickbooks-software-integration/
Note that Dan Wernikoff, Senior VP at Intuit, has been leaving comments in several of my articles in the blog.
Blair, you have a reasonable concern. However, given the REASONS that they made this change, I would SPECULATE that Intuit won't be pulling the SDK. What isn't clear, at this time, is HOW MUCH support they will give the SDK moving forward.
And, as we have seen for several years now, things can change...
I want to change my app from a paid version to a free with ads. However, I don't want the people that originally paid for the app to get the ads.
I was thinking I could include a new update that has extra code that sets up some UserDefaults saying the version doesn't have ads and then do the update to the free version. But that doesn't seem like a very reliable solution.
I think, it depends on minimum OS version, that your program can be run on. For iOS 5.0 and later you can try to use iCloud to store some flag about purchased version. It allows you to set this flag not only for one device, but for the user's account.
Or you can store this info in the keychain to get it later. But in this case your user will not be able to have no ADs on some other device with his(her) account.
Anyway, as far as I know, you need to create an update for your app first to write this flag anywhere. And only in some time make an update with ADs.
I will be glad to see comments if someone has another thoughts about this issue.
It seems there is no reliable method to detect whether someone paid for your app or downloaded it later when the price has been changed to free. For this reason I have decided to create two separate entries in the app store.
I am working on application in which i am implementing In-App-Purchase,On buying the product through my application i can fetch all the information regarding the products in my console, but the problems occurs where i am not getting the pop-up from App Store which shows all the information to buyers. I cannot figure out the problem. Please suggest some solution for this.
Thanks.
Apple's IAP backend (test mode) has been up and down over the last 5 days, mostly down, there's been no official confirmation of the outage, just check twitter for similar complaints.
need code.. or follow troy brant's awesome tutorial
http://troybrant.net/blog/2010/01/in-app-purchases-a-full-walkthrough/