After many searches I did not find a solution to the matter.
I'm publishing an app developed in flutter on the appstore. After loading in xcode the compilation is not available in appstoreconnect.
This is happening for new builds.
I started trying in December and so far I haven't found a solution.
Below the appstoreconnect image without the button for new compilation available.
Related
I recently uploaded a TestFlight external test build to iTunes Connect. When users download the application the Share Extension doesn't seem to be appearing in Safari or any other application that has the share menu. Even after clicking the more button the application extension doesn't appear at all.
Any reason why this might be happening? And any ideas on how to fix it?
I had this same issue occur with a few of my testers on an early TestFlight build. After I uploaded a new build that had the exact same share extension code it was no longer an issue.
It should be noted that I contacted the original poster about this issue and he had the same experience.
I think this can be attributed to a TestFlight bug that works itself out over multiple builds.
EDIT
I found out that one of my users was using iOS 10.2. While the deployment target of my main app was 10.0, the deployment target of my Extension was at 11.2. This prevented my share extension from working for them.
Lesson: Make sure your deployment targets are the appropriately set across all your targets!
Using Visual Studio 15 with Cordova plugin we submitted our iOS app version 1.0.0 (major.minor.build) and discovered an issue. We rejected the app in iTunes connect and increased the build number to 1 to get around error ITMS-4238 in application loader suggesting that the same app with the same version number is already submitted for review, which is correct. The remedy would be to change the major, minor, or build number for the new build. However, after changing the build number in config.xml the app builder still shows the ipa built for version 1.0.0. In fact changing the major/minor/build seems to have no impact on what the app builder sees as the version number for the built package as it continues to show 1.0.0.
Any suggestions as to what step we are missing would be greatly appreciated.
Thank you in advance.
OK - Here's the answer to the riddle. The build process from Visual Studio creates a brand new ipa file on the Mac and does not replace the existing ipa. The application builder automatically points to the existing build, which you would be trying to replace in the app store. So in order to pick the new build you have to do a search when browsing for the package using the application builder, sort by date, and pick the latest ipa file.
I downloaded Xcode 7.1 from the App Store today after working from 7.1 beta downloads from developer.apple.com and have a new iOS app build to upload. So I did:
Product > Archive
Upload to App Store (or Validate)
But the response was:
You are not authorised to use this service
Intriguingly, when I 'Export' the build to the Desktop and then use Application Loader 3, it uploads without error.
Is this an iTunes Connect bug? Or is there a new Xcode checkbox I've missed?
Note: I've also tried removing and re-adding my AppleID as suggested here, and restarted my Mac for good measure (which actually allowed the validation to work once), but still no luck uploading directly from Xcode > Organiser.
I met the same issue today and I think it is a bug of Xcode 7.1
Finally I managed to submit my app via Application Loader. There were warnings but it did work.
Here are the basic steps:
Archive
Export
Xcode menu --> Xcode --> Open Developer Tool -->
Application Loader
Double click "Deliver Your App" and choose the
file exported in step #2
click next and follow the instructions until
the end
Here's the quick solution:
Don't use Xcode beta versions to submit apps for release — it's beta for a reason and shouldn't be used with production code.
Submitting Apps
Apps that are created using beta versions of Xcode or that are built
for beta versions of operating systems will not be accepted on the App
Store and Mac App Store. Apps that you submit should be developed
using the latest version of Xcode from the Mac App Store and should be
built for publicly available versions of iOS, OS X, and watchOS —
except when GM seeds are available. When a GM Seed of Xcode becomes
available, use it to develop your app for submission. When GM seeds of
iOS, OS X, or watchOS become available, build your app for these
versions.
↳ https://developer.apple.com/support/pre-release-software/
Having the same problems as all of you, just thought I'd share that I found a way to Validate successfully, you have to disable the "Include bitcode" checkbox before moving forward. As for the actual upload to App Store, no work around for that one other than use the Application Loader...
Also I've been seeing this too since XCode 6.4, but it seems once the current version has a couple of months after it's originally released it starts working again... fingers crossed that it starts working again soon, because uploading straight from Organizer is so much better. (I saw the Beta Version post, when I say after a couple of months for current version I'm not talking about Beta versions, just in case ;) )
Same problem here.
Downloaded Xcode 7.1 from the App Store and it refuses to upload a new version.
Happily Application Loader worked ;)
Hopefully this gets fixed quickly.
One possible reason for the issue could be multiple development accounts under one name (personal and company). I've read elsewhere (apple radar) that that caused earlier problems of this kind.
Happens here if the dev account is only admin. I had to use the central account for uploading our apps. I think this problem startet sometime with XCode 6. Didnt investigate further though since Application Loader works in cases when I dont have access to the central account.
I also have the same problem today.
Finally, I used the application loader to upload successfully,too.
Theres a few solutions I have come across to solve this issue.
Most common being to remove and re-add your developer account.
This won't work on its own though, you need to also 'view details' on your account and have Xcode download your provisioning profiles again.
The other alternative is to upload your build using application loader. The disadvantage to using this solution is that should you be trying to upload using a beta build of Xcode or OSX you won't be able to change your apps .plist in the archive folder to trick iTunes connect into accepting it. In this instance all you have access to is your ipa.
Disable the "Include bitcode" checkbox worked for me.
I'm updating my existing app to include support for Apple Watch (at this stage just handling of notifications), however when I archive my app and try to submit it to the app store for review I continually get this error.
I've tried playing around with the build settings and I've also tried googling the error, however I can't figure out what the issue is.
Does anyone have any ideas or has anyone come across this issue too?
You cannot submit an app for review using a beta version of Xcode.
Following today's Apple Watch official release, Apple updated Xcode to version 6.2 which in theory should allow submitting apps that contain Watch extensions. However I just tried to submit my app that includes support for Watch using the new Xcode, and got the same error. I hope this will be fixed sometime soon on the ItunesConnect site.
I have a PhoneGap application which works in the Xcode simulator. I also am in the Apple Developer Program so I can do code signing to run apps on actual devices.
However, I am having a hard time finding a good resource to walk me through the exact steps to get the app on my physical iPhone/iPad. I have found other guides which are either for Xcode 3, or they show how to get PhoneGap working in the emulator but not how to get on an actual device, or they are presumably using a different version of Xcode 4 because they reference different commands than I have.
If you have successfully deployed an application from Xcode 4 onto an iOS device, could you please post a link to steps that you used or refer a book that has that information? I appreciate any help that anyone can give on the subject. Thanks!
[Edit: Though I am using PhoneGap, the steps to deploy from Xcode to iOS device are AFAIK the same.]
[Edit to add more detail:
I have my project made and it runs on iPhone 4 simulator and iPad 4 simulator.
I also can plug in my iPad (already went through the assistant to get it provisioned), select it in the scheme list box, click the Run button and it will launch as expected on the iPad. Does this mean that I have the code signing part working at least?
So far so good. Now I want to make a build so that I can distribute to people to test the app on their devices (I have their UDIDs already). When I get to the "Publishing Your Application for Distribution" section of the iOS Development Guide in the iOS Developer Library, I get stuck in the Archiving Your Application for Testing section. I am having trouble finding the Code Signing Identity build setting. It also looks like they have changed the menus around because they refer to a Build > Build and Archive menu item that doesn't exist anymore. I tried Product > Build for > Build For Archiving which seems like the closest option and the build actually succeeds but in the Organizer > Archives tab there are no archives.
Sorry that I do not have more specific information about where the process is breaking down for me but I'm new to the Xcode environment. I can typically figure these things out on my own as long as there is documentation somewhere but I have not been able to find any that match my build of Xcode. Thanks!]
[Edit again: After doing more research I ended up following the suggestion of others and did a complete uninstall/reinstall of Xcode which ended up resolving the issue albeit in a rather heavy handed way.]
You'll want to check out Apple's Documentation, for sure:
iOS Development Guide: Managing Devices and Digital Identities
iOS Development Guide: Building and Running Applications
They have a complete walkthrough of provisioning, building, and deploying your application to a device.
The Xcode Organizer makes it fairly straight forward and painless now... but there are still some sticking points, and reading the documentation will give you a full overview of exactly what's going on in the process.
Contrary to apple advise, setting Skip Install (Build Setting) to NO fixed this. Using phone gap here.
Archives not showing up in Organizer for XCode 4
Once you have your Apple Developer Account Credentials, You can follow gist I have created:
Apple's Code Signing Process