Most of my project increase the build number fine using Xcode UI, but there is one that stopped doing it and I am struggling to remember to change it in the info.plist so I was hoping there was a way to fix it.
Changing the version number as shown in the below image from the general tab of the target changes it for all of my dozens of apps, except one that only recently stopped, which I wouldn't be surprised if the reason was that I accidentally changed a setting or something:
I archive this specific project and even though the version number is 1.5, it still shows 1.4 unless I change it in the info.plist, as shown below (after I changed to 1.5):
Is there a way to fix this? Its frustrating when I look in the organized when I'm ready to submit the app and see the wrong version number when I just waited 15 min to build the archive for the app.
I did just recently upgrade to Xcode 14, but I've submitted 4 apps this week and this is the only 1 that this is happening for.
Thank you!
Sup gang
I've noticed dsyms link is no longer available under Build Metadata in App Store Connect. Our team has submitted a couple of builds recently and none of them have it. Looks like the last build that had it was over a month ago.
I've seen many old posts asking the same question before so I wonder if this time Apple devs broke it again or is it a new default?
I have the feeling it won't be there ever again as we have disabled bitcode in our project (so Apple does not re-generate the dsyms).
Anybody experiencing the same problem?
I'm having problems uploading my app version since I upgraded Xcode to 13.3.1
The compilation succeeds as always, but when I'm doing the process of uploading and distributing to the App Store I get this screen with no explanation:
I have cleared the cache, clean the build, and changed the node version from 14 to 16 and I haven't been able to make it work.
Thanks
After many attempts, I solved this by setting the Team to NONE and then back to the signing team.
This is under the Signing tab.
I have downloaded and used Xcode 8 beta, and uploaded my app to the Appstore with that. That didn't work because of it being from a beta version of Xcode, however after I tried to open the same project in Xcode 7 again, I got the "No matching provisioning profiles found"-error when archiving and trying to re-upload. How can this be fixed?
I used half a day trying to figure this out, so thought I should post it here in case someone else gets into the same problems.
I tried just about every solution I found here, but nothing worked. I ended up going back in my git-history finding that when I had used Xcode 8, it had added two of these lines to my project.pbxproj file:
DEVELOPMENT_TEAM = XXXXXXX
After deleting these lines (reversing the hunks in my commit-history) everything worked as normal.
I released a new version 6 days ago. I see some crashes in iTunesConnect analytics, but none in the crashes organizer, nor does my release even appear in the "version" dropdown within the crashes organizer.
Normally it takes a day or two after a release for crash reports to make their way into the Xcode Crashes organizer, and anecdotally I've seen the crashes appear in the Xcode Crashes organizer about the same time as in the iTunesConnect analytics website.
Interestingly, the previous versions still show in the "version" dropdown and I can see reports continue to trickle in for them. There is a steep decline in crash reports for that previous version, presumably as most folks have moved to the latest version.
On a new machine, with a fresh XCode install (but linked to the same developer account) I see the same behavior. Maybe it's a problem with my developer account?
Update 2016.09.01: Two months later, new releases are still not showing up in the releases dropdown automatically. The workaround posted below to manually add them has been working great, but hopefully I don't have to do it forever. I have to assume this is a problem with my local setup as this can't be happening to everyone. Let me know if you figure out a long term fix.
Update 2016.10.13: The work around isn't working for my most recent release. I again see crashes in ITC, but after manually adding an entry for the release in Info.json, I see "No crash information is available for this release."
Update 2016.10.15: I guess the work around is continuing to work, the crash reports were just delayed by an extra 48 hours.
Update 2016.1.20: At some point, (maybe around mid december, XCode 8.2?), I started to see new releases appear automatically again, and no longer have the joy of manually editing my XCode config data every time I push a build. Other than updating XCode, I can't think of any way I might have "fixed" it.
It's likely a bug with Xcode/ITC services. I filed a radar (#27277793) yesterday and was on ITC tech support today. If you're having this issue please report it to Apple and reference the existing radar (#27277793) so Apple can recognize we're having the same problem and prioritize a fix.
A workaround to get the crash reports for my latest release was to manually add a new entry in the crash organizers Info.json.
In: $HOME/Library/Developer/Xcode/Products/<bundle.id> edit the Info.json and add a new entry to the beginning of the "productVersions" array based on the existing entries, but change the build number to whatever build the crash reports are for.
You also must update the appStoreStatus field depending on whether your app is in TestFlight or in the AppStore. appStoreStatus: 1 for TestFlight and appStoreStatus: 3 for AppStore.
After relaunching Xcode and going to the crashes organizer I watched as the last 6 days of crash reports came in.
Yay for human readable configuration data!
Had similar issue where Xcode crash reports stopped updating after we increased our deployment target iOS version. Fix was to edit Info.json like mentioned above and remove all unsupported OS versions from "supportedOSVersions" array of latest build that was appearing in "productVersions" array.
This worked for me when none of the above answers did.
Find the Info.json file as described above in mkirk's answer. Make a copy as a backup. In the productVersions section remove any unneeded versions. As you can see below, "productVersions" is a json array, and it will contain a series of json objects, each of which represents one of your versions. I desperately needed crash reports for a recent release to the app store and after deleting all versions preceding that (below it) and restarting Xcode, voila! the Organizer suddenly began showing all my crash reports.
"productVersions" : [
{
"version" : "4.0.45",
"productType" : 1,
...
Remove the entire $HOME/Library/Developer/Xcode/Products/ directory. Quit and restart Xcode and then run Organizer. They all come through after that.
Please follow below steps,
Remove bundle from Xcode products using,
rm -rf ~/Library/Developer/Xcode/Products/com.yourapp.bunlde
Restart you Xcode and open Organizer
Make sure that itunesconnect sites are accessible
Xcode->Organizer is supposed to download all crashlogs from beginning. Hope that helps.