Ive submitted my first app and it has been approved. But I have a few issues that i'd like to ask what I should do about.
One of my images/icons that I have in my app showed correctly in my distributed binary at my end (running it in debug simulator from xcode) but on the app downloaded from the app store it is not showing at all?
IPads cannot see my app in their search of the app store?
IOS 4 is needed to run my app. How do i change it so that it can be run on IOS 3 aswell? And if i make it IOS 3 compatible does this mean that it cannot be run in the background at all (i.e. when the close out of my app and go back into it will it restart the entire app)
Also does anyone know whether submitting an update is quicker in the review process than submitting a entirely new app?
Thanks in advance for your help
Thats a QA issue. The simulator is just that and if you want to be sure that your App runs as you expect on hardware then you need to check it on hardware. There are instances of images that decode on simulator but not on hardware.
iPad only runs iOS 3.2 at the mo so if your app runs on 4.0 it wont show up for iPad.
See 2 and no you dont have multitasking in 3.2 so you need to make sure your app state persists across atomic launches. You'll need to remove/conditionally compile any 4.0 only API in your App. If thats a problem wait until November-ish.
Maybe, depends, probably no. Lead time on update/new submission is around 8 days +/- YMMV.
Related
I released version 1.1 of my app in App Store a few days ago. In this version I added a splash screen and shell and changed the name of the app bundle to info.plist. With this, the name of the app is displayed differently than version 1.0. Also i added a support e-mail button to send the user email to me. Before releasing the update app, I tested it on physical iphone and simulators. Everything worked wonderfully. Now the app update is published in the store and when I update the app and start it, the splash screen loads but nothing more. The app just crashes and I can't see why. My question:
How can I find out why the app crashes? Are there logs from App store? Does someone have an idea where the reason can be?
Many Thanks
I have a need to update my managed app running on a large amount of iPads without any user interaction. These devices all have the managed app locked in Single App Mode. As I understand it, it's an iOS limitation that an app cannot be updated if either of the following conditions are present:
The app to be updated is in the foreground.
Any app is locked in Single App mode.
With our use case, both of these conditions are present. I also understand that the current workaround is to do the following:
Disable Single App Mode.
Enable Single App Mode for a different app (e.g. Safari) to bring that app into the foreground.
Disable Single App Mode.
Update app.
Re-enable Single App Mode for your app when the update finishes to bring it back into the foreground.
While this method works, it has a lot of drawbacks:
It's highly manual, we have not found a way to automate it. This is especially a problem as the number of devices becomes large. Internet connections can be spotty and there is no robust way to ensure that each step has executed for all devices.
It's prone to failure. Especially between steps 4 and 5 above. It seems there are little to no guarantees of when/if an update was successful to know definitively when to re-enable Single App Mode.
It fails for devices that are offline at time of update. If a device does not have internet connection when the update is executed, there is no way to guarantee that the steps execute fully and in the correct order the next time the device comes back online.
I am looking for a scalable solution to reliably update my managed, Single App Mode app running on thousands of devices in an automated way with no user interaction. I am using Meraki for an MDM right now, for what it's worth.
With iOS 11.2 you can now push a silent update to a device with it running SingleApp mode.
Apple failed to mention this to the public but is included in the beta notes.
Called Enterprise Support today, They could not find any official documentation mentioning ios 11.2.x supports the updating of apps while in single app mode :(
Now with iOS 11.3 beta it is working again but after updation, app is not automatically locking in Single App mode we have to restart device.
Hope in upcoming beta's this issue will get addressed.
iOS 13.1 beta 1 seems to fix most of the issues I have been having in this area.
I had seen issues in iOS 11-12.* where updates sometimes worked, but sometimes showed a pin-pad even though no passcode or guided access code was set, or otherwise behaved strangely.
In the 13.1 beta 1 you can push an App update and nothing will happen on the device, but if you send a restart command afterwards the device will restart, update the App and continue in single app mode.
I have tested with both 'Single App Mode' (SAM) and 'Autonomous Single App Mode' (ASAM) and it has worked every time for me so far.
This works for my use case as you can push the update anytime and schedule the restart at suitable time when the device is not in use.
edit: 13.1 beta 2/3/4 changes this, now when you push an update from your MDM the App will close, update and re-open and continue in single App mode. I checked both SAM and ASAM both now update without the need for a restart.
I have a strange problem with my app. I have finished the design and I am ready to update it on the store however, when I do that and I test my app using test flight the app is completely different from the version installed from xcode.
Some colors are different the are bugs that are not present when testing it on xcode and even the status bar that I have hidden is now visible..
I have other apps on the store and i never experienced this isuues and I am sure that I am uploading them right version of their app..
What could be going wrong?
I uploaded an app to the App Store a while ago, but I have to delete the iPad support for different reasons. I am not talking about removing the app from the iPad App Store, only removing the iPad support. The Developer website states the following:
Developers who wish to issue updates, but remove device support, have three choices:
Fix their app so that it can work on the devices they originally set out to support.
Target a newer version of iOS that requires a newer device.
Remove their app from the store, and upload the new app with a different bundle ID.
The problem is that if I remove the app from the app store and upload it again, I can not use the same app name. That is not an option.
Is there any way out of this mess?
Answering my own question - no, there is no other way! I ended up creating a decent looking iPad app to fix the problem.
Apple will not allow you to remove support for iPad if you ever offered it on a given app name. Further, the app has to be well enough designed for iPad that Apple likes it enough to allow it to pass. We had an app rejected for this reason.
first of all, I know there are many questions similar to this one, but, they are old and the answers in them unfortunately no longer work, since the game has changed without Hacklo.us to do part of the process.
Basically, I want to develop for iOS and test the apps I make, and later in the future I may want to submit them to the Apple Store, but for now I'm not willing to pay 99$ to join the Apple iOS developer program just to use my apps in my iPhone.
I have a jailbroken iPhone 4S with iOS 6.1.
The only posts I found about how to do this, either use Hackulo.us (that went down about 2 months ago) or something called Jailcoder that is also offline and they also seem to work with only old versions of XCode/iOS (not clear about that point).
Any new progresses on how to to this with the present conditions?
Simple. After building the app, just use some utility (SSH, iExplorer, etc.) to copy the app bundle to the /Applications directory on the device. After that, either run the uicache tool or respring the iPhone to make the application appear on the home screen.