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.
Related
I have created a developer account for two weeks, and now I want to submit my first App. However, when I click new app, the bundle ID list does NOT show the project I would like to submit, but It do show some projects I used to practice. I have look up a variety of solutions on internet, including sign out and log in again, or clean up my Safari data. I have suspected some reason, but I'm not quite sure if it right?
First doubt : some SDK import?
The Bundle ID shows on the list are some small project I used to practice when I was a beginner. Recently, I have tried to use some SDK like Facebook SDK and Firebase. Facebook and Firebase works fine on my simulator and iPhone devices. So I'm not quite think this might be the reason, nut just type on in case I missed something
Second doubt : Xcode version?
When I tried to using Firebase, since iOS 13.3.1 seems not to support, so I update my iPhone to iOS 13.4.1. However, the Xcode should also be updated to 11.4.1, otherwise it cannot connect to my devices. When I look up the bundle IDs listed on App Store Connect, I think those projects are created before I updated Xcode. The project created after updated not showed on the list. But I have created too many projects to practice, so I'm not quite sure I remembered right. I suspect this might be the reason, anyone else met the same problem after updated Xcode?
By the way, there is also a strange thing confused me. I have deleted some projects I used to practiced on my MAC, but they stilled shown on the list... I have manually deleted on my Apple Developer Web.
1) Go to https://developer.apple.com/account and set up the app with its explicit bundle ID.
2) Then go to https://appstoreconnect.apple.com > "Create new app" > Select the previously created bundle ID.
This does not really have anything to do with SDK usage or Xcode setup. (Automatic code signing might do some steps for you, but the most bullet-proof way is mentioned above)
This is an app I'm helping out with remotely. I have some issues right after cloning repo..
Assets folder is marked as modified. git status results: modified: AppName/Resources/Images.xcassets/AppIcon.appiconset/Contents.json. One of many compile warnings says "A 1024x1024 app store icon is required for iOS apps". Is new 1024x1024 asset placeholder the modification that was made?
Many warnings:
The app is running well in App Store and has support for iPhoneX, so if I clone, shouldn't all this stuff be sorted out already? I still see layout issues when I run in simulator on any device size that were apparently fixed for iphoneX compatibility. When I was running Xcode 8.3 I didn't have these issues.
I need to add a feature, push and make build available on TestFlight, but I'm worried about pushing with all these compile errors & bet it wont even archive with missing 1024x1024 asset.
Question:
Should I just go back to previous version of Xcode rather than sticking with 9.1 or resolve all this stuff myself? Devs aren't really available for me to consult with since initial app was developed through full-service software dev company.
Im mainly in contact with business ops/project managers who don't really have knowledge of tech at this level. Im no seasoned dev myself so I'd like some advice here before expressing concerns with managers or getting strings pulled to talk with devs who last worked on it.
I'm hoping the first comment isn't that this question doesn't belong here. I think its a fine line.
Thanks for your time.
The app in the appstore could be submitted and released to the appstore with issues listed in the issue navigator of the xcode on posted screenshot.
So, switching to a version of Xcode which was used for a last submit to the app store by previous developers does not guarantee that those issues will be not present.
There is only one issue which you have to resolve is "1024x1024 app store icon is required for iOS app" and this can be done only within Xcode 9
UPDATE 2 :
We have at last a crash log : https://www.dropbox.com/s/62sq0ybyr4mhkkh/Screenshot%202015-09-02%2012.26.54.png?dl=0
It seems that a library is not loaded...
UPDATE 1:
Here's what we have :
- no crash log on Xcode with a device where the app crashes at launch
- We didn't run the app via Xcode, we downloaded it via Diawi
- We plugged the iPhone on the Mac, we didn't run the app via Xcode, we just looked at the crash log (nothing to see). After we unplugged the iPhone from the Mac, the app launches perfetecly ! Besides, when we uninstall the app and install it again via Diawi, it launches perfectly again !
- So the simple fact that we plugged the iPhone to the Mac makes the app work.
Any idea ?
Below the first message
I have a serious issue with my iOS app, here's what we know :
The app has been approved on App Store
But if we download it via App Store promo codes (it's like a private beta), it crashes at launch, mostly on iOS 8.3 or below.
We had the same issue by adding UDIDs and sending the app via Diawi before the submission
We have already an app on the store (let's call it v1) and we have submitted a new version (v2) which has been a new project on Xcode.
The crash happens with people who had already the app v1 as well as people who hadn't
The crash remains even if you uninstall the v1 and install v2
We put crashlytics : impossible to get any crash report, it crashes before the init, although we can see the launch page with the logo. We tried to put a delay of 10 seconds to let crashlytics initialize, but it doesn't last untill the 10 sec
Weirdest thing : when we plug the device on Xcode to see what happens, then it works ! Impossible to see the crash again. Then, even if you uninstall and repeat the process by installing via Diawi, it will work ! As soon as you plug the iPhone on Xcode, it will always work...
Some people told us that it crashes and it works the day after.
What we did :
We updated the Pods
We changed the certificates and provisionning profiles and made it clean
We had some issues due to the Parse SDK, but we fixed it
The target is iOS 7.1
Here are the pods that we have (screenshot):
https://drive.google.com/file/d/0BzHfUya4Va4rb2dQSVJYazN1MFBxcG1DQnpBNXAybU9SVzk4/view?usp=sharing
Has someone seen already such an issue ? The weirdest thing is that Apple hasn't rejected it.
Thank you for your help !
So I had exactly the same problem today with my app Macro Defense: https://itunes.apple.com/us/app/macro-defense/id955086416?ls=1&mt=8
I found that by turning wi-fi off on the device, the app runs perfectly. If this is also the case with you, then my guess is that the problem lies in trying to perform some network functions in the appDelegate.
Have contacted apple support, and will repost if I get a definitive answer to this.
Cheers!
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).