-
Notifications
You must be signed in to change notification settings - Fork 84
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
android:foregroundServiceType="" while building with eas #2556
Comments
Hi, I don't see an Android manifest in your example repo. What do you by |
I’ve been working with a plugin that adds the permission android:foregroundServiceType="microphone". When I build using EAS (either locally or in the cloud) and examine the APK’s manifest (using APKtool extraction or Android Studio) on Ubuntu, I notice that android:foregroundServiceType="" appears instead. However, when I inspect the same APK’s manifest on an iMac, the android:foregroundServiceType="microphone" value is correctly present. The strangest part is that if I build the APK using Android Studio, I see android:foregroundServiceType="microphone" even when checking the manifest on Ubuntu. This suggests that it’s a bug related to the display or retrieval of the value, not its actual presence in the APK. |
This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed. |
This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem. |
Build/Submit details page URL
https://expo.dev/accounts/mullersq/projects/notifee-test/builds/b3cd3d57-0609-4219-9843-d4f9be639e7c
Summary
When I build with EAS, some values for android:foregroundServiceType are deleted (microphone, camera), and I have android:foregroundServiceType="" in manifest instead of android:foregroundServiceType="microphone" while building with Android Studio.
Minimal exemple: https://github.com/FurankuSQ/notifee-test-eas
Managed or bare?
Bare
Environment
expo-env-info 1.2.0 environment info:
System:
OS: Linux 6.8 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 18.17.0 - ~/.nvm/versions/node/v18.17.0/bin/node
Yarn: 1.22.21 - /usr/local/bin/yarn
npm: 10.8.2 - ~/.nvm/versions/node/v18.17.0/bin/npm
SDKs:
Android SDK:
API Levels: 33, 34
Build Tools: 30.0.2, 33.0.1, 34.0.0
System Images: android-34 | Google APIs Intel x86_64 Atom, android-35 | Google Play Experimental 16k Page Size Intel x86_64 Atom
npmPackages:
expo: ~51.0.28 => 51.0.32
expo-router: ~3.5.23 => 3.5.23
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.74.5 => 0.74.5
react-native-web: ~0.19.10 => 0.19.12
npmGlobalPackages:
eas-cli: 12.3.0
expo-cli: 6.3.10
Expo Workflow: bare
Error output
No response
Reproducible demo or steps to reproduce from a blank project
https://github.com/FurankuSQ/notifee-test-eas
eas build --profile development --platform android
Manifest:
The text was updated successfully, but these errors were encountered: