The APK is signed with a different certificate. Be sure to use the same keystore and key as used for
I keep getting this error when trying to upload my apk to applab, and i have already checked google and idk how to solve it. "The APK is signed with a different certificate. Be sure to use the same keystore and key as used for a previous version." Even though i have changed everything, i have looked through my keystores and there is only one that uses the key i have made.
How to submit a 2nd build to the same release channel?
I just uploaded my first build to Applab If I upload a new build with the same package name (e.g; com.project.name) regardless of release channel, Meta says the names cannot match https://ibb.co/crpP9sR If I change the name (e.g; com.newProject.name) then Meta says the names must match https://ibb.co/FBcynjb
app store review comes back with same error
Hello, I have made multiple submissions of different code of my application and the Meta reviewer keeps coming back with the same error: stuck in loading mode with unity logo in one eye. This however, is not what I can see when I load it from any quest or open it from the Meta Quest Developer Hub. I have tried now for 4 different builds and they keep coming back with the same error I do not see. Please can somebody help, does anyone else have this issue? Thanks
AppLab: How to pop up a warning about space required
When I click "Get" on this app's store page: https://www.meta.com/en-gb/experiences/6511679575602893/ I get a lovely little popup that says "This app requires a minimum play area of 2 metres by 2 metres. Please ensure that you have enough space before continuing." How do I get this for my own app? I thought it would be the 'Supported Player Modes: Roomscale' setting, but I added that to my own app and I don't get the same popup: https://www.meta.com/en-gb/experiences/7074530125915038
My App's OBB file is not being installed properly. This issue comes out of the blue...
I've never had an issue before the most recent Quest updates. Uploading new build .apk with .obb file sizes over 4.4gb total. When I try to get passed the first scene, the game's next scene will not load. This has never been an issue before and no lines of code have been changed. I was able to catch one of my fresh installs not properly installing. After I exited the game, the update button suddenly appeared even though it had already fully downloaded and installed the proper version number. This issue was confirmed by several players. I don't know what to do here. None of my new builds are allowing me to go passed the Main Menu even though it works flawlessly on PCVR. I suspect it has something to do with the .obb file not properly installing. I am in desparate need of help.App don't start after updating from AppLab
My app I am developing is not starting after an update until we restart the device. We are using Unity 2021.3 with addressables and spliting the app into apk and obb. Seems like the addressables are not correctly found after the update. It happened in incremental updates (few megabites) but also updates that downloads apparently the whole app again (1.1 GB). Then after restarting the headset it opens with no problems which makes me believe it is something wrong with the update process. Does anyone had this issue. Would be great to hear from the Meta team as well.
Assigning IAPs to to an existing AppLab release is not possible.
I have an AppLab release currently in Production with some DLCs attached to it (all marked as Free) and they can be downloaded within the App itself. I have just added two more DLCs with min-version-code set the my current Production release. The addins were released in the Platform Services -> Add-ons page and assets were uploaded using the ovr-platform-tools. When I go to the build page (that is on AppLab Prod) the newly added Addons are listed but I can not edit their price or the Required option. When the price is not set, it is impossible to download the addin programmatically within our App. The "Edit" button is simply grayed out. How can I simply add new DLCs to an existing Production release?
