I am developing an app which uses settings bundle to store information. Few users who have updated to the latest version reported that all the settings previously stored has been cleared. This hasn’t happened in previous versions and doesn't occur in iOS 8.x.x, only occurs in iOS 9.0. I use NSUserDefaults API to read/write app settings.
Does anyone else experienced this problem? Or if you could you please let me know any causes for this problem and possible solutions.
Thank you.
Related
I have an issue related to update new version in iOS 11.
I have created a function to detect new version and prompt user to update via configuration file. This function works perfect so far.
But after upgrading to iOS 11, when I tap on Update Now of alert popup, then AppStore is opened, the status of button is Open instead of Update, even thought current version of app on AppStore is 2.0 and current version of app in device is 1.0 !?!
I guest user has opened App Store previously and AppStore has cached content for next use. Finally, the bug is occurred! This is just my thinking!
If you got this issue or you have any ideas on this issue. Please share with me.
Thanks,
Ryan
Sometimes it also happened to me. when an app is updated, and I can not install the latest version, it shows me OPEN not UPDATE on AppStore, and I have to uninstall the app, download new app on AppStore, and it is the latest version.
I think the reason why we can not download the lastest app version is AppStore needs time to update its database, or maybe it has cache or somthing.
I had an obj-c project which I later converted to Swift. When the users of the obj-c app try to update it to the Swift version, the screen turns blank and the app gets terminated. However, when the app is uninstalled first and then newer version is installed, there are no crashes. FYI, I use a bridging header in the Swift project which uses some old files. I also use HockeyApp to see crash logs but since app terminated directly from launch, I have no feedback. I'd really appreciate any help and insight on this.
Thanks a lot!
The update process is completely handled by iOS. There is no code you can write that could interact with the update process itself. The code you write for update needs has to run in the app process itself.
So if you have a crashing bug or issue in your app that causes it not to start properly, there is nothing you can do other than getting a crash report from the device and fix the bug in your app.
I've ran into quite an odd problem today. Today my app successfully got onto the app store. However, when I downloaded it I immediately noticed that the apps basic functionality wasn't working. It just hangs when trying to get outside information. I went back to my xcode project, ran it and it worked perfectly. I removed the app store version, and re-deployed the xcode version to my phone, and again it worked perfectly.
Did Apple do something to my code? The part that messes up seems to be a where my app creates a NSURLSESSION that is used to gather data from a website. Perhaps they "cleansed" the url strings that I use? This functionality that messes up is crucial to my app and hasn't been changed since I've submitted to the app store.
Anyone have any ideas why this is happening or how to fix this?
Thanks
Just posting the "solution":
Edit your Scheme and set the "Run" build configuration to "Release". After saving that, clean the project (cmd+shift+k) and run again on your device. By default, that will make you run the app in your device just as it will be ran when published in the AppStore.
And yes, unfortunately you will have to wait another week for Apple to aprove your app's new version as it will go through the review process again. Good luck! :)
For me it was that I was using old promocodes for testing.
That promocodes were from old version of the app (ios downloads app version that corresponds to promocode version), but I was expecting new functionality. So use latest promocodes!
I am not that familiar with iCloud integration. I read numerous bad reports about the integration in iOS 5 and 6. But now I guess it's better in iOS 7 so I decided to add it in one of the new apps I'm working on.
From what I read and saw in the WWDC 2013 CoreData/iCloud video I thought it was as simple as flipping on iCloud in Xcode and configuring the NSPersistentStoreUbiquitousContentNameKey value to something unique in the addPersistentStore call, to get started. But each time I run the app, in the simulator or on a physical iPhone, the console output shows the iCloud setup failed due to URLForUbiquityContainerIdentifier returning nil.
I am using Xcode 6 beta and the iOS 8 beta 2 SDK. I've made sure iCloud is signed in and otherwise functioning on the simulator and physical devices. I've also made sure that the "Documents/Data" switch is on under iCloud setting and the app IS appearing here. I've also browsed to the simulator application directory and I see the SQLite file in the normal documents directory and in an iCloud directory.
Is there something really simple I'm missing?
There is bug in Xcode 6 beta version , i am using Xcode6 beta 5 and facing same problem.
I changed key com.apple.developer.icloud-container-identifiers to com.apple.developer.ubiquity-container-identifiers" (ubiquity, not icloud). Then add an item to this as "iCloud.$(CFBundleIdentifier)". In "Capabilities" tab Xcode will show error in red mark but don't fix it , leave as it is.
If solved my problem and i am getting Url now.
Not sure what the developer agreements allows to say, but at the time of writing this, it is still beta and most probably is a bug in xcode 6. There may be a few threads on the developer forum on that exact same subject. Search for 'URLForUbiquityContainerIdentifier' and you may find more information.
Try beta 4. My iCloud code is now working.
You didn't mention configuring your app ID for iCloud access and updating your provisioning profile, so that's probably the problem. The device needs to know that your app is allowed to talk to iCloud, and it does that based on the provisioning profile. You'll need to go to the iOS developer site and:
Update the app ID to add the iCloud capability
Regenerate the provisioning profile so that it includes the new capability
Download a new copy of the profile and make sure that you're using it in testing (it's best to delete the old copy first just to be sure).
I've updated my app from iOS5/iPhone 4 to iOS6/iPhone5 compatible. The app was approved by the apple store and is available to download, when downloaded from the app store it crashes on start-up. However, installing the app from xcode onto devices works perfectly, I'm at a loss. I've attached a link for the crash report
any help would be most appreciated
http://pastebin.com/epgh2Jxv
Delete the app from your device completely, clean the product, then run again from xcode. I bet the problem comes out on yours too. It seems that a storyboard doesn't exist. You probably removed it by mistake but it is still existing cached in your product since Xcode doesn't actively go searching for old files to delete.