When the user selects "Reject" on my Terms and Conditions page, I'm able to display an alert, but I can't figure out how to exit from the application completely. Is there a way to do that?
Apple discourages apps from quitting themselves—it gives the user the impression that the app has crashed—and based on the fact that I've never seen an app display terms-and-conditions nonsense when it starts up, I'd guess that that's a surefire way to get your app rejected from the Store in any case. iTunes Connect allows you to provide custom license text when you're submitting the app; I'd recommend just using that.
I just faced this challenge and thanks to #Noah Witherspoon I found how to set a custom license in order to be shown before downloading the app from AppStore. Please refer page 52 of the iTunes Connect Developer Guide in order to see what would happen when you do that.
Related
I'm getting ready to submit an App that relies on the user being at specific locations to watch a video. (Kind of a mashup of geocaching and youtube.) Needless to say none of these videos are anyway near Apples headquarters. So how will the App store review people be able to properly review the App? Do I have to provide test data in their vicinity or can I instruct them to fake their geolocation to a location that works?
I guess the best way is to just submit it once, wait ~7 days and see what they have to say,
but since they have special toolchains to test apps, it shouldn't be a problem.
Just make sure to mention it in the review notes.
I've submitted an update to an app once that requires an user and password to login, and gave them a test user. When I checked the server logs, they never logged in once - but the app was still approved.
The iOS Simulator can 'fake' its location :) Though I doubt what they DO review in their process, because once they accepted one of my Apps' update which crashed upon launch...
Recently had to deal with this myself... submitted a location specific app without any extra review notes, and the app got rejected. In the rejection notice I was given the instruction to create a video of the app in action and then provide a link in the review notes.
So I used another iPhone to take the video, put some basic explanation text in the video using iMovie, uploaded to YouTube, put the link in the reviewers notes, re-submitted the app and then 5 or so days later it was approved.
As I understand, they review team does NOT test the usability nor stability of your app during app reviewing. All you need to do, is to provide an testing account, and some sample data, screenshots to them helping understand how your app works. If the app does not show any data because of a reasonable circumstance, it's not the problem of your app quality nor user usage, but data coverage. So you won't have problem with it.
I know this has been asked previously however I would like to disable the home button for an in-house app which will be distributed internally across iPads.
I have searched for a solution both on here and Google and would like to stop users from putting the app into the background. I have seen one solution which doesn't seem to work under iOS 4.0 which opens the app up again when the home button is pressed.
Could I make use of any private APIs to do this seeing as this is an internal app and won't be reviewed by Apple for the App Store?
Thanks
I don't know why this is down voted so much it is a perfectly legit use case for an internal enterprise application. Kiosks, POS etc.
Anyway anyone wanting to know how to do this should see my answer here Lock-down iPhone/iPod/iPad so it can only run one app
Whatever your reasons are you are not able to do this.
Apple provides no functionality to perform this action through their API. You might want to re-think your strategy. Look maybe instead for a physical barrier.
Additionally you might want to look into JailBreaking and iPhone since you say it is only for internal development and won't go to the appstore. A jail broken phone might allow you access to change the home button behavior, though I cannot confirm this since I have never had need to code on a jail broken device.
If it's your iPad, glue or bolt a cover over the home button. Connect the iPad to Xcode or iTunes to halt and/or reload your app.
But note that knowledgable users will still be able to reboot the device by holding down the lock button.
Jailbreak and add incarcer app can disable the home button (admin has a code to allow activation). Then you're locked in your app. If you're up for jailbreaking, seems like a great solution.
There's a new hardware solution, adhesive-backed aluminum home button covers. They allow home button activation through a pinhole, using a paperclip (similar to many popular metal encosures). http://bubcap.com/bubcap-pro.html
Finally, thanks to most of you, I got my first app approved by Apple. The problem is that I'm only able to find it on the app store if I click on the link provided on iTunesConnect.
If I try to search with any of the keywords I inserted in the metadata I don't find my app.
One more thing the link is like this:
http://itunes.apple.com/us/app/gearup/id441500177?mt=8&ls=1
does the "/us/" mean that it is only on the american app store. I didn't select any specific country (they are all selected).
thanks
You can remove the /US/ from the link. You're just seeing that error because the US store is not your default.
The link works for me and shows your app on itunes.com before launching the iTunes application
Your searches may not work until your app has been propagated to all the various stores. Sometimes that can take a while.
Immediately after going live and having been accepted, there will always be a small amount of time while the app propagates across the Apple servers.
Your link works as koregan stated, and yes the /us/ is the country code. For example, if you replace it with fr then you see the web page in French - if you localized the app then you will see the app information with the text you would have supplied; else you will see it in English.
This link shows a video where an app upgrade is "forced" from within the app itself:
http://buzzworks.de/blog/update-ios-beta-apps-from-within-the-app
The App Store is not called in and it's said to work only for AdHoc
apps.
Anyone knows how is this possible?
edit: please give a look to the video before answering. AdHoc apps are signed by the developer and they do not come from the App Store. This sort of forced update is useful when doing beta testing and in enterprise applications.
I've found that it's all explained here:
http://developer.apple.com/iphone/library/featuredarticles/FA_Wireless_Enterprise_App_Distribution/Introduction/Introduction.html
The developer should create an .ipa with the app and a manifest in plist format with the URL to the .ipa and a few other things.
The app can optionally implement its own way to find if an update is available and open
the URL to the manifest.
I didn't it's really possible because the app has to somehow sign itself. The best I can think of right now is that the app is not signed?
You can always force people to go to the app store when a new version is out. Simply make the app connect to a webservice first. Other solutions are not accepted by Apple, or will quite simply not work because of other issues (signing is one of many).
You could also design your app in such a way that forced updates are never a requirement. You can load your user interfaces from the web (Apple has presented some valuable information about that during the previous WWDC), your data can come from the web, and if there is any other correction to do just ensure your app is backwards compatible.
That's how the app store works. And it never requires a 'forced update' ... Well, almost never ;-)
It seems like Info.plist file has an ability to declare different roles for the same application bundle through the UIRoleInfo key. SpringBoard can recognize these roles after installing an app and may display separate icons for each application role.
For instance, iPhone shows MobileSlideShow.app as 2 different programs: Photos and Camera.
Unfortunately, there is no official Apple documentation about the subject at the moment. Would anybody advise how to organize the same behavior in a custom app?
This feature is going to be used in the Enterprise product for ad hoc distribution.
This isn't a supported feature, so if you do this you might have a hard time getting your app through the approval process. I wouldn't recommend using it.
Have you tried it to see if it works? If it doesn't work, you could create a second app that does nothing but launch the first one, with a custom URL scheme. The first app can recognize when it is being launched with that URL. This is not ideal as you will see the second app launch & quit (though it should be really fast).