I am a new developer. I bought a console account and generated, signed and published the key to the game I finished from Unity. Then, the Android App Bundle is not signed during the app installation phase.
gave an error. I contacted support and they said they updated my key but the problem still persists. can someone help? google is responding very slow my game needs to be released before fridayenter image description here
Related
I have a problem when trying to test an application on macOS. For reference, this was created in Unity.
The BundleID has been changed as a previous developer had used a very odd naming format, codesign and notarization works on the new app.
However, when I try to run the app it starts complaining about the app being purchased on another computer (which is correct, we still use the old version for testing) but it has been removed on this device and hidden in the App Store.
Anyone know anything else I can try to get past the problem of macOS knowing about the old app version.
If you log in it then just says the app is corrupt as I am guessing it is comparing it to the downloaded App Store version.
Solved it myself, apologies for taking up bandwidth. In Unity untick Mac App Store Validation in Player Settings-> Other Settings
My app works fine on release mode and debug mode, I even send a published apk file to a friend to install and works fine too. But today when I finally released my app on play store I discovered that registration with phone number doesn't work anymore, more exactly my app doesn't send verification code now.
So, the problem was not about Firebase Database Rules.
The problem was that I provided SHA-1 signing code generated by Android Studio in Firebase Project Settings.
The fix was about providing SHA-1 signing code from Google Play Console to Firebase Project Settings. Hope this helps somebody!
I have signed my electron application on Windows with an Code Signing Certificate. According to https://www.electron.build/code-signing, the app will show "a warning during installation that goes away once enough users installed your application and you've built up trust".
My question is, what is the number range of users that have to install my application in order for my certificate to be trusted?
This is crucial for us since we are launching a beta this week and would like to avoid showing the message.
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.
I started some days ago a small Mac app for Mac OS X Lion. I've never uploaded a Mac app before, so this is the very first time.
This is what I've already done:
Created App ID
Created Certificate
Installed Certificate
Created a Production Provisioning Profile
Changed the App ID to my generated one
Created a new Configuration based on "Release"
Changed its Code Signing to 3rd Party Mac Developer Application
Selected the "Production"-Configuration which I created for the Archive-Scheme
Archived the Application
Now I wanted to "Share" the Application. Xcode (4.1 btw) said to me, there were no valid signing identities. Does I need to add an Entitlement.plist like in iOS? Have I forgotten something?
Update:
I just figured out, that I have to sign my app twice. I've still selected "3rd Party Mac Developer Application" but I can't select the Installer cert while submitting my app.
Have you installed the WWDR intermediate certificate? I just had the exact same problems and my issue was that the intermediate certificate was not installed on my machine. Granted, nowhere does Apple explicitly say you need it installed, more like suggestions. But, you do need it. You can find it here, or by going to Developer Certificate Utility under the Mac Developer Center.
I got it to work. I deleted my App and created it new.
I didn't create a new Configuration, and I only changed the Code Signing Indentity of the Target to 3rd Party Mac Developer Application. After this, I archived the app and then I was able to select the installer cert.