Forum Discussion
Solved
Invalid package name when updating app
We are working on a new app. I uploaded our first apk via Meta Quest Developer Hub, which succeeded. Now, when I try to replace the build with a new version, I get an error regarding the package name already being in use. The package name in use is the one used in the initial build and in the update build.
This post seemed to have the same issue: Invalid Package Name - Meta Community Forums - 522751 However there was no further discussion on what happened or how to fix it.
I can't find any specific point of potential failure. I've increased build number, tried a custom manifest as well as not, and even changed the package name, which then gave me the error that the package name is different from the original.
Using
Unity 2022.2.6
OpenXR 1.6.0
In case that anyone is still looking for a solution, I was able to upload a build yesterday using this tool
https://developer.oculus.com/resources/publish-reference-platform-command-line-utility/
./ovr-platform-util upload-quest-build --app-id <app-id> --app-secret <app-secret> --apk <path-to-apk> --channel LIVE // Optional fields: --assets-dir <path-to-DLCs-dir> --obb <path-to-OBB>
10 Replies
Replies have been turned off for this discussion
Experiencing the same issue. Uploaded a build to Alpha release channel, when trying to upload a new build via the Meta Quest Developer Hub, I get "The package name is already in use for another application. Every application must have a unique package name." error. I've incremented the version + bundle version code with the same result If I change the package name, it says it must be the original package name.
Has anyone managed to fix this? I uploaded a test build earlier today, now I'm trying to update it but I can't.
Had to keep moving forward so deleted the app and created a new one 😅
Did deleting the app and creating a new one fix the problem? I have this same problem and deleted the app, created a new one but the same problem persists. First upload goes fine but after that I get the same failed error message "The package name is already in use for another application. Every application must have a unique package name."
No, it just helped get through the problem for the first upload as you mention.
I can't provide insight into whether deleting the app helps, as this is not an option for us, as we've been approved for app lab with the original build. I've submitted a bug via MQDH. Have not heard back. Do Quest devs monitor these channels? We've got our launch scheduled in less than a month and I am unable to update our application.
CJ.mayastem I just tried to reupload, no luck. And deleting then creating a new app gives the same error, though maybe the system just needs time to remove the old app.
VRTogether_Company I really hope so. I'm just trying to apply for Oculus Start right now so I can afford to delete and recreate apps, but I'll be in the same position as you in a few weeks. I've submitted a bug report but who knows how long that'll take.
I've found a workaround, it might help someone
https://developer.oculus.com/resources/publish-reference-platform-command-line-utility/
./ovr-platform-util upload-quest-build --app-id <app-id> --app-secret <app-secret> --apk <path-to-apk> --channel LIVE // Optional fields: --assets-dir <path-to-DLCs-dir> --obb <path-to-OBB>In case that anyone is still looking for a solution, I was able to upload a build yesterday using this tool
https://developer.oculus.com/resources/publish-reference-platform-command-line-utility/
./ovr-platform-util upload-quest-build --app-id <app-id> --app-secret <app-secret> --apk <path-to-apk> --channel LIVE // Optional fields: --assets-dir <path-to-DLCs-dir> --obb <path-to-OBB>I was able to upload successfully using the CLI tool as well. Interestingly, it was still failing with the package name issue when I used the token parameter, even though that was given as an example in the reference docs: Oculus Platform Utility Reference | Oculus Developers When I changed from token to app secret, the upload was successful. Seems like a bug with authentication. Thanks materialisemedical !
