I lost the developer signing keys for the playbook in a hard drive crash. I tried applying for new keys, but have not got a reply back. Tried to mail them too but no reply. Is there a way to get signing keys in 2020 for the playbook?
I believe Blackberry team monitors stackoverflow for legacy support.. Hope they can help me.
Please check your inbox and spam folder for the BlackBerry PlayBook signing keys now. There were some requests that were held up that have been processed now.
Related
I have an updated version of an old Xamarin Android app I want to release. I previously set up the signing key which I used to sign the app previously. Apparently, a few months ago I updated to the Google app signing mechanism, but apparently I still need to sign the app myself before uploading. But if I use my old script mechanism, Google tells me "You uploaded an APK that is not signed with the upload certificate." I can't figure out how to set up the signing with whatever that upload certificate is. Neither the Google nor Xamarin docs are comprehensible to me. I downloaded "upload_cert.der" and "deployment_cert.der" files from Google, but have no idea what to do with them. I tried using Visual Studio to publish, but it says to create Oauth client and enter the client ID and secret, pointing to the Google Play Console, but I can't figure out how to do that. It would be really nice if there were some docs for people in my situation.
Somewhere along the way I must have regenerated the keystore, which no longer matched the key Google has. I found a backup of the keystore, restored it, and now it works.
I am trying to generate the required certificates to build Apple App, but I get a runtime error while adding a new device via the certificate wizard.
The error reads (RuntimeError) Please login using Spaceship::Portal.login('user','password')
Before trying to generate a certificate I first connected successfully to itunes connect with my credentials. The error seems to be related to Fastlane presumably used internally by CodenameOne to generate the certificate.
Moreover I also tried to remove one character in the UDID and I got the same error which is estonishing. However the UDID has been double checked with someone who dictated it to me. So the UDID is a 1-to-1 copy of the one shown in itunes.
Why do I get this error message and what can be done to remove it and be able to add the new device ?
Please note : My setup involves codenameone running under Eclipse Mars under Linux 64.
Any help appreciated!
Thanks for reporting this. It should now be fixed. Please give it another try.
I am creating an in house MDM solution and have managed to create everything I need in terms of the MDM server, SCEP server etc in order to gather information about our devices.
However, I am having an issue pushing the Enterprise Apps that we create. I can push the apps to the device (and they install without issue) but I am still presented with the 'Do you Trust this developer' prompt.
I was under the impression that Enterprise Apps should be trusted by default when deployed by MDM. I have tested this using Apples Profile Manager and indeed the application is installing without issue and does not require the user to trust the developer.
I am obviously missing something obvious but have been chasing my tail trying to find out what it is!
Any help would be greatly appreciated.
Thanks in advance
David
OK. Turns out the issue was actually not much better that a typo!
Having uploaded the app to my server, I had a manual creation of the manifest for installation. The app identifier in the manifest did not mach the actual app!
So... weirdly the app was pushed via MDM, the manifest was downloaded (and appeared under the control of MDM briefly) then iOS realised mad things were afoot so booted the app out to the normal enterprise installation process (untrusted developer dialogue etc).
Fixing the manifest bundle identifier to match the app fixes the issue.
That's many hours I'll never get back!
I am guessing you are missing a CA certificate/root certificate that you used to sign your app. Due to this iOS might have been unable to trust the app since it was not able to confirm the validity of the signing cert.
I'd like to send another developer an Xcode project of mine to debug. Are there any issues with security in doing so? I.e. developer keys and such. Form what I understand, the key will be in my keychain on my Mac, so the Xcode project folder should be fine to send. Am I correct in this?
That's correct. Compressing and sending your XCode project will not reveal any of your sensitive developer info, only plaintext passwords and such in your source code.
You won't send any of your developer credentials, but you will be giving the developer the intellectual property that is contained in your project.
I'm developing an iOS application which needs access to the system certificates and keys for digitally signing data.
I've done some research and I've found that theoretically it's not possible from a third party app to get access to the system keychain since it only has access to its own keychain. Here is a stackoverflow post explaining that.
However, some applications like the Cisco AnyConnect show a list with all the system certificates for VPN configuration. That might mean that THERE ACTUALLY IS a way to get that system certificates list.
This image shows how the certificates are displayed in the cisco app.
I'd be really grateful if somebody could shed some light on this issue.
Because it's just a matter of signing your binary using a proper entitlements.xml file. Keychain-dumper does exactly what you're looking for.