App Deep Linking Fails After Feb 9th OS Update

My reports

Submit feedback

Investigation titles and descriptions are summarized by AI from Meta based on reports submitted by developers

Expected behavior

Issue

2 similar reports

Created 3 days ago

Add your report

Suggest an edit

Copy link

Category

Platform Services > App Deep Linking

Platform

Unity

Investigation summary

After the Feb 9th OS update to build 5205633.10050.150, deep linking between two apps developed with Unity 6000.0.58f2 and Meta SDK All in one v81 stopped working on Meta Quest 2 and Meta Quest 3. The apps were using the Meta documentation for deep linking, with hardcoded app IDs, and were working before the update. Now, when attempting to launch one app from the other, nothing happens. Logs show that the error 'User is not entitled for appid 31122667217381243' appears, which is an app ID from another app in the organization, not related to the two apps being tested. Additionally, PackageNotInLibraryDeveloperException errors occur with the same unrelated app ID and the package names of both tested apps. Despite adding try-catch blocks and verifying the code execution without errors on the Unity side, the issue persists, suggesting a problem with the OS update or Meta SDK interaction.

Latest official response

Meta's Response:

Entitlement checks are failing because com.Virtualisurg.LauncherTest is calling Platform.initialize() with the wrong application ID. Older OS versions were more permissive, but on newer OS versions this failure blocks subsequent PSDK API calls. Please update the app ID used for Platform.initialize() in com.Virtualisurg.LauncherTest to match our records: 32837166569207826.3/3/26 at 10:08 AM

Still need help?

Tell us what you need support with and we'll find the best solution for you.

Get support

Get answers from the community

If you're having trouble, find answers to your questions from Meta Quest users around the world.

Go to community forum