AnimatedDebug is using depricated global.Expo.Constants object (SDK40)
See original GitHub issueDescription
After upgrading to expo SDK40, I started getting this warning:
Your project is accessing the following APIs from a deprecated global rather than a module import: Constants (expo-constants).
The global "__expo" and "Expo" objects will be removed in SDK 41. Learn more about how to fix this warning: https://expo.fyi/deprecated-globals
After a bit of investigation I found that it is caused the use of global.Expo.Constants.appOwnership
Steps To Reproduce
just use expo SDK 40 and react-native-reanimated
Expected behavior
No warning is caused
Actual behavior
Package versions
1.13.0
Could some one fix this and create PR?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Expo Constants - Depreciated global? - #11 by kemikalgeneral
Hi,. I've just updated to SDK40 and i'm getting the following warning: Your project is accessing the following APIs from a deprecated global...
Read more >Expo SDK 41 - DEV Community
SDK 41 includes React Native 0.63, the same version as in SDK 40. ... you will not be able to use remote JS...
Read more >EXPO + react-native-reanimated debug issue - Stack Overflow
The new APIs in react-native-reanimated@2 use React Native APIs that are incompatible with Remote JS Debugging. Consequently, you can only debug ...
Read more >expo constants - You.com | The AI Search Engine You Control
Basically, the constants are an object with multiple values depending on the ... that a third-party module is still using the deprecated expo...
Read more >How to use the expo-constants.isDevice function in ... - Snyk
util.Map org.unimodules.interfaces.taskManager.TaskInterface.getOptions()' on a null object reference" modules.push(optionalRequire(() => require('./tests/ ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks to @brentvatne this fix will be probably patched in the Expo SDK and I’ll backport it to the v1, so everyone’s versions should keep working.
I understand v2 has been released. Does this new version address/fix this issue we’re all experiencing in our apps that use Expo SDK 40? A response, one way or another would be appreciated. Thanks!