expo: expo-notifications relies on Constants manifest, installationId, deviceId, and linkingUrl and throws warnings in bare projects

Summary

I’m using expo-notifications version 0.12.3 in a bare project, and it throws the following yellow box warnings:

Constants.manifest is null because the embedded app.config could not be read. Ensure that you have installed the expo-constants build scripts if you need to read from Constants.manifest.

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.

Constants.deviceId has been deprecated in favor of generating and storing your own ID. This API will be removed in SDK 44.

Constants.linkingUrl has been renamed to Constants.linkingUri. Consider using the Linking API directly. Constants.linkingUrl will be removed in SDK 44.

Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare!

bare

What platform(s) does this occur on?

Android

SDK Version (managed workflow only)

No response

Environment

Expo CLI 4.7.3 environment info: System: OS: macOS 11.2.3 Shell: 3.2.57 - /bin/bash Binaries: Node: 14.16.0 - /usr/local/bin/node Yarn: 1.22.11 - /usr/local/bin/yarn npm: 7.18.1 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4 Android SDK: API Levels: 25, 28, 29, 30 Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.0, 30.0.2, 30.0.3 System Images: android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom_64 IDEs: Android Studio: 4.1 AI-201.8743.12.41.7042882 Xcode: 12.5.1/12E507 - /usr/bin/xcodebuild npmPackages: react: ^17.0.2 => 17.0.2 react-native: ^0.64.2 => 0.64.2 npmGlobalPackages: expo-cli: 4.7.3 Expo Workflow: bare

Reproducible demo or steps to reproduce from a blank project

N/A

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 19 (2 by maintainers)

Most upvoted comments

I just installed expo-firebase-analytics and created a custom hook for it - now I suddenly saw this warning. No idea where its from as I’m not using react-native-uimodules so it might have different sources too

Dinkelborg on Nov 25, 2021

Yes, it logs an array with the font types available 😃 I don’t have an error, only the warnings I mentioned.

MEsteves22 on Oct 6, 2021

I only started having these warnings when I installed expo-notifications in my project. Before that, everything was fine. That’s why I thought it did rely on these constants.

I’m going to check the rest of my project though.

Thanks!