Encountering Error adding public keys for Knox Enabled App: "Error binding KEA license key and package"
I'm trying to get a feel for the workflow of developing a Knox Enabled App. I've started this process by simply pulling the KEA Sample App (https://seap.samsung.com/sdk/knox-enabled-app/sample-apps - the VaultBank_0 app) into Android Studio, building it and pushing the apk onto a Samsung tablet.
The first time I do this I get the "App not authorized" modal and am offered two buttons, "CANCEL" and "OPEN ANYWAY". I click "CANCEL". I then download the Public Key Extractor and generate the public hash key (as per steps 4, 5, etc of the 'Setup (source code)' section here: https://seap.samsung.com/sample-app/get-started-knox-enabled-app). Everything I'm doing looks like this: https://seap.samsung.com/html-docs/android-knox-enabled/Content/KNOX-Ena...
Now, I have a public hash key and package name in hand that I've emailed to myself, so I swivel over to here https://seap.samsung.com/license-keys/associated-to-apks and, in the "Knox Enabled App keys" section, I expand the 'Development' type and choose to "Upload additional APK" (specifically the "Or manually upload your APK package name and public key hash." radio button) and paste my values in there.
Voila... All is well, now when I go back to the tablet and open the sample app. I no longer see the "App not authorized" modal and I see the sample app has been installed and has the KEA badge overlaying it's icon in the apps selector screen.
That was all context, and now I'll get to the problem.
I have a 2nd tablet that I want to install this same sample app on (imagining that the KEA I'm developing will need to be pushed out to multiple devices b/c there are multiple developers and testers and such). I go through this very same process on the 2nd tablet, and when I get the point where I paste in the "Package name" and "Public key hash" here https://seap.samsung.com/license-keys/associated-to-apks for the 2nd device, I click 'Add' and I get an error message back that says "Error binding KEA license key and package."
So, where I'm at now is, it seems like I can't run the same KEA (ie, an app with the same package name) on multiple different devices, under the same credentials I log in with on the seap site. I've got to be doing something wrong, or just misunderstanding the domain. Seems like I should be able to do this, but I suspect I'm misunderstanding something.
- Encountering Error adding public keys for Knox Enabled App: "Error binding KEA license key and package"
- App not authorized!
- Getting Error 206 when activating ELM License Keys
- Information on Samsung encryption for DAR
- Prerequisite apps inside the KEA container
- SecurityException: Admin does not have MDM_HW_CONTROL or KNOX_HW_CONTROL