I have a first version 1.0.2 of an app, in the Internal testing section of the Google Play console. I have successfully downloaded the app via the Google Play app in my Android smartphone.
I am now trying to update the app, but in I get the "Your Android App Bundle is signed with the wrong key." error. There are multiple solutions suggested for this error, I am about to embark on them...
In the meantime, I succeeded in uploading a version 1.0.5 of my app to the Pre-registration tab. It is ONLY in that tab and I can't find any way to share it with other tabs, or to download it to the smartphone. I'm not sure this it the best place for it, for the moment I am testing the app myself, I don't have an army of people to release the app to. That version 1.0.5 is listed at the bottom of the Pre-registration page, under App bundles for supported devices.
I don't see how I can transfer that version 1.0.5 to the other tabs of the console and download it. It does not appear when clicking the Add from Library command in other tabs. In Internal Testing there's a Promote Release command to move the releases there to Closed testing, but in Pre-registration I can't find any such command to move the release anywhere else.
Related
I am making an app that collects information from Apple Health (HealthKit). When the application is installed for the first time, the apple screen appears with the permissions that will be used, but when it is in Testflight that screen never appears, is there any extra configuration that has to be done when it is released to production?
if the app is installed from xcode, it works correctly
I had two different bundles, one both in the card of my app and another service that I have OneSignalNotificationServiceExtension. Within both they must point to release and not to debug. that's what i did and it worked in testFlight
Is it possible to upload an app archive to the App Store in Xcode 7 beta for internal testing with Test Flight?
Has anyone been able to do that?
Note: I am asking about submission for prerelease internal testing with Test Flight. I am well aware that releasing the app to the public is not possible from beta versions of Xcode.
Update
I was able to use Xcode 7 beta and upload binary to the App Store's prerelease section. After that I was able to open it from the Test Flight. Code Signing identity was: iOS Developer. Provisioning profile was "Automatic". Both values were set for Debug and Release.
Yes, you should be able to upload your application via beta Xcode 7. But, the problem is to have potential bugs and that's also why they name it beta. You should take this as a risk when you decide to upload your application via new Xcode. It's okay to go with this way if you are handling your personal application. For your client or business, it's the best to use a stable version.
I am using Phonegap Build to quickly deploy and test my applications. For this to work, I had to go through an elaborated tutorial on creating provision files and certificates and borrow a Mac to make use of Keychain. By then however, I only registered one device UDID.
Now I want to add more devices, but I dont want to go through the whole process again, also what if I have to add other devices later?
So I was thinking to use Testflight, which only requires that you upload an .ipa file (apart from having a developers account etc). With Phonegap Build you can easily create these .ipa files.
However, since I am working with Windows, I dont see how I can upload the .ipa files on Testflight. Most tutorials online talk about using Xcode and some other Mac program.
Is there any way to upload it anyway?
Hacks might be available but since Apple integrated TestFlight into iTunes Connect - which (at this time) does not have a public API - the only official solution is to use Xcode or Application Launcher for ipa uploads. Both are only available for OS X.
An alternative solution might be to use an iOS CI/CD (continuous integration and delivery) service to do the upload. We happen to have one - bitrise.io, CTO here - but you can find a couple of other services as well.
I am having an issue where:
When using the same computer I use to distribute apps to the app store, I am able to successfully package up an app so that beta testers can install apps on their devices using TestFlight.
I have a second computer that I have transferred all the code signing items from this computer over to, using the Export/Import Feature in XCode.
I have spent a few days trying to get the same process to work in TestFlight.
I am able to successfully archive the app and load it up to test flight, but when Beta Testers try to install the app, they get the familiar alert: "Unable to Download Application".
The installation icon gets about 3/4 of the way through the progress bar before this alert appears, which leads me to believe there's a problem with the provisioning profile.
I have tried to clean out and reinstall the Team's code signing Export file multiple times and have arrived at the result.
Additionally, I have gone through the process of getting rid of TestFlight, it's Provisioning Profile and Cleared Cookies, Data, & History from Safari.
Any help would be much appreciated.
Check that you have built and signed your App using a Provisioning Profile for Distribution!
Use "Automatically manage Signing" option in XCode for code sign signing instead of exporting the Certificates and use there. I use 'fastlane' for pushing the builds to Testflight on daily basis. It saves developers time too.
Last night we have released a free app in the Mac AppStore. The app didn't yet show up when searching for (parts of) the title, however, we could find it by searching for one of our existing Mac Apps and clicking through to our 'Developer Page'.
When 'buying' the app (it's actually free), the icon pops up in LaunchPad and the progress bar for downloading & installing shows. Under Snow Leopard, the icon pops into the Dock and the progress bar for downloading & installing shows.
However, in both cases, as soon as the progress bar is filled, the app directly disappears from the LaunchPad / Dock and can no longer be started.
I've checked my Applications folder, but the app is nowhere to be found. I also checked this on other systems (under user accounts that never develop in XCode), those showed the exact same problem. I've also tried downloading a few other free apps from the Mac AppStore on my own system, these downloaded and installed successfully and don't disappear.
There seems to be a problem with our app that causes this issue, but I have no idea what it could possibly be. I didn't find anyone else suffering from this problem.
First and foremost, I would love to know what causes this so we can fix it.
Secondly, I am wondering how this app ever came through Apple's review process having this issue.
Any ideas?? Thanks in advance!
An Apple Dev on the Apple Developer Forums answered this question:
Do you have a copy of that app elsewhere on the system? App Store will install it over an existing copy, whereever that copy happens to be.
A different user on my system had previously built a debug build of the app from XCode. Apparently, any downloaded versions of Mac Apps are written over those apps -- even if the old version is within the home folder of a different user on your system, any version you purchase/download from the Mac AppStore will overwrite thát version; effectively locking out the downloading user from the app that he may have just paid for.
Imho, that's a crappy way of handling 'updates'. But it's good to know our app is working fine.
Thanks for the help StilesCrisis!
Update: Apple has asked me to file a bug report for this issue, will do.
I'm developing an app on Electron, and for me problem was that I had build files in my project folder, even after I deleted the app which I installed with .dmg in Application folder. So, it seems Mac Store looks throw whole disk space and trying to find app with same app ID, and if it exists, don't rewrite it.
After deleting my .app and .pkg build from the project folder app successfully installed from Mac Store. If it will not work for you, please try to clean app related folder in these directions: ~/Library/Caches and /Library/Application Support. I did it before, and can't guarantee that removing only project build files can help you. Maybe these actions are somehow connected. And removing app build files do not work for you.