My earlier version of the app was uploaded years ago. Now I wish to upload an updated version. The old one was an APK file and now it has to be an AAB package (developed using Android studio). When I was uploading some new app yesterday I underwent a process of getting errors at package name level and more. I have not 'updated' an app yet and the process is new to me. I wanted to know of there would be issues especially with recent changes?
I am looking for some helpful pointers and links that will guide me. I am kind of new to this
I am trying to upload the build to AppStore but it is not showing in Testflight or anywhere. Its shows there for a few seconds and dispear. I am getting the Xcode project from unity. I have tried multiple apps and multiple unity versions and multiple accounts as well all builds are disappearing. And I even tried uploading an old Xcode project that was successful 2 days ago. I even created empty unity project and tried uploading but it still disappears. It all happened after apple's latest update 12 hours ago. anyone else having the same issues?
I am. I've loaded 5 builds and even changed the version number of the app. The new version number showed for a few minutes and then disappeared. No build was in the dropdown though.
Update:
Just got off the phone with Apple. There's an "import issue" that I need to wait 24hrs to clear. I did receive an email from them about the error and assumed it related to only one upload but it seems to have jammed up my whole upload/Testflight.
Can anyone suggest what to do about this message that I get when submitting my Xamarin Forms app to the iOS store?
Comment on possible duplicates
This question was asked before and not answered; I don't think an answered duplicate exists.
This is a known issue which was recently closed by the Xamarin team issue can be found here https://github.com/xamarin/Xamarin.Forms/issues/7323
And the fix is and i qoute
All the bits are in place, solution time! TL;DR: all is described in this piece of documentation here.
Make sure you are using the latest Visual Studio (for Mac) on the stable channel, that should put you on the right path. At the moment, you will need to use the Xamarin.Forms 4.5-pre1 preview release. I understand that this might not be an option for all of you, but rest assured, the stable package will be out well before the deadline. Stable 4.5 is planned mid to end of February.
Lastly, put the --optimize=experimental-xforms-product-type flag into your iOS additional mtouch arguments setting and you should get rid of the deprecation warning by Apple. If you don't have any references of your own to UIWebView of course 🙂
I would like to ask you to try this at your earliest convenience. Maybe not to release an actual new version to the store based on the Forms preview package, but at least upload a build to verify that this solution works correctly. Whenever you do, you can just update to the 4.5 stable package and release a new version with confidence.
If you do run into anything with this solution, please feel free to reach out to me directly (gerald.versluis [a with a long tail] microsoft.com) or open a new issue on the repository. Of course positive feedback is always appreciated as well 😉
I'm preparing to open source an XCode project I've been working on privately, on Github.
I am planning on using Github's release feature and and tag the initial release as 0.1.0. This much I know.
But I have one question: What's the best practice for the version number and build id of the XCode project itself going forward?
Do I need to update the version/build-id every time raise a version on Github?
Should these numbers be synchronized?
p.s.
I know some people may try to close this saying this is "off topic" for Stackoverflow, but trust me I tried asking everywhere else and nobody answered. And I do think this type of question is relevant to Stackoverflow.
For the 2cd question, whether you need to update the version on GitHub depend on you. If you make huge changes for your code, maybe you can create a new release.
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.