Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Constants.installationId has been deprecated #79

Open
tomelsner opened this issue Nov 25, 2021 · 6 comments
Open

Constants.installationId has been deprecated #79

tomelsner opened this issue Nov 25, 2021 · 6 comments

Comments

@tomelsner
Copy link

Getting this message when calling the constructor in an expo 43 project. Is there a plan to address this and implement the generation of an installationId with one of the suggested methods here: https://forums.expo.dev/t/constants-installationid-how-to-implement-it-on-your-own/50003 ?

@gregdburns
Copy link

Seconding this.

There are two warnings from Expo, so perhaps both can be considered.

  1. Constants.installationId has been deprecated in favor of generating and storing your own ID. Implement it using expo-application's androidId on Android and a storage API such as expo-secure-store on iOS and localStorage on the web. This API will be removed in SDK 44.
  2. Constants.platform.ios.model has been deprecated in favor of expo-device's Device.modelName property. This API will be removed in SDK 45.

Potentially as a quick solution a property could be exposed that would allow the implementer to set a unique app id that could override the usage of Constants.installationId? In our case, that would be ideal, as we already have created a custom app Id for other use cases.

@watadarkstar
Copy link

watadarkstar commented Feb 6, 2022

I'm also getting this warning. Any plans to address this @ryanvanderpol or are you open to contributions? I might be able to take this on or find someone who is willing to.

Started to see this warning after I upgraded Expo to SDK 44 and installed this library for our open source meditation app:
heylinda/heylinda-app#140

We have an issue tracking this here in our app:
heylinda/heylinda-app#142

I will probably start with a patch-package solution.

@ryanvanderpol
Copy link
Member

Contributions are always welcomed!

@tomelsner
Copy link
Author

@ryanvanderpol could you merge one of the pull requests that fixes the issue with SDK 44?

@minusthebear02
Copy link

@ryanvanderpol , any news on this? looks like there are some PR's opened to solve these deprecation issues

@bcarradini
Copy link

I found a publicly available package that was forked from this repo and that claims to be compatible with Expo SDK 44.

The repo: https://github.com/meecodebymariomurrent/expo-analytics
The changes: master...meecodebymariomurrent:master
The package: https://www.npmjs.com/package/@meecode/expo-analytics

I'm going to give it a try, but still hope that @ryanvanderpol will merge in one of the PRs that addresses compatibility with SDK 44.

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

No branches or pull requests

6 participants