Skip to content

Fix: APPLICATION_ID meta-data read as Integer instead of String, breaking DAT registration#49

Open
kbaker827 wants to merge 1 commit intoIntent-Lab:mainfrom
kbaker827:fix/android-application-id-string-type
Open

Fix: APPLICATION_ID meta-data read as Integer instead of String, breaking DAT registration#49
kbaker827 wants to merge 1 commit intoIntent-Lab:mainfrom
kbaker827:fix/android-application-id-string-type

Conversation

@kbaker827
Copy link
Copy Markdown

Summary

  • android:value="0" in AndroidManifest.xml is parsed by Android's Bundle as java.lang.Integer, not String
  • The Meta Wearables DAT SDK expects a String for APPLICATION_ID — getting null back breaks the deep link construction for the registration flow
  • Fix: move the value to a strings.xml resource (<string name="mwdat_application_id" translatable="false">0</string>) and reference it via @string/mwdat_application_id, which forces Android to treat it as a String

Fixes #13

Test plan

  • Tap "Connect my glasses" on the home screen
  • Confirm the Meta Stella app opens without showing "Erreur lors de l'ouverture du lien"
  • Confirm logcat no longer shows KEY expected String but value was a java.lang.Integer

🤖 Generated with Claude Code

Android's Bundle interprets inline integer literals as java.lang.Integer.
The Meta DAT SDK expects a String for APPLICATION_ID, so it gets null back,
breaking the deep link registration flow with a silent error.

Reference the value via a string resource to force String type.

Fixes Intent-Lab#13

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix: APPLICATION_ID meta-data read as Integer instead of String, breaking DAT registration

1 participant