expo: [SDK 45] android block permissions warning looped

I’m occurring the same issue.

I can’t reproduce this with expo-cli@5.4.7 and this is resolved in @expo/config-plugins@4.1.5 with this PR which removed the warning entirely.

If you are experiencing this in your project then it is likely that you have a version of @expo/config-plugins installed that is lower than @expo/config-plugins@4.1.5. You can run npm why @expo/config-plugins to see where that comes from.

i am also having the same problem. It’s constantly printing in every 5 sec in terminal and I can’t stop it. My mobile app works fine tho

Hey, @kbrandwijk, the issue occurs exactly as I pointed on the previous comment. here is a repro. This project was upgraded from 44, not clean inited. I’ll test with the clean inited one now.

EDIT: Occurred with the clean inited one too. The conditions seems to be adding a plugin on expo.plugins in app.json or on plugins on app.config.js heres the repro on a clean inited project

Hey, @kbrandwijk, @brentvatne, I noticed that yesterday version 5.4.4 of expo-cli was released, on the changelog it includes the PR that appeared to fix this. After updating the cli today, I still get

~/i/app ❯❯❯ yarn wsl --dev-client                                                                                     main ✱ ◼
yarn run v1.22.18
$ REACT_NATIVE_PACKAGER_HOSTNAME=$(netsh.exe interface ip show address "Wi-Fi" | grep 'IP Address' | sed -r 's/^.*IP Address:\W*//') expo start --dev-client
Starting project at /home/ivopr/ictio/app
» android: block-permissions: No permissions provided
» android: block-permissions: No permissions provided
» android: block-permissions: No permissions provided
Developer tools running on http://localhost:19002
» android: block-permissions: No permissions provided
» android: block-permissions: No permissions provided
Starting Metro Bundler
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
█ ▄▄▄▄▄ ██▀▀▄▄▀▀▄ ▄▀█▄█▄██▄██▀█ ▄▄▄▄▄ █
█ █   █ █▀███ ▄█▄▀▀    █▀█▀█▀ █ █   █ █
█ █▄▄▄█ █▄▄█▀▀██ ▄ ▄▄█▄ ▄ ▄▀█▄█ █▄▄▄█ █
█▄▄▄▄▄▄▄█▄█ ▀▄█ ▀ █ █▄█▄█▄█ █ █▄▄▄▄▄▄▄█
█ ▄▀▀█▄▄ █ █▄▀▀██ ▄▄▀ █▄ ▄▄ ▀█▀██ ▄▀███
█ █  █▄▄█ ▄▄█▀ ▄▄▄█▄▀▀▄▄▀ █ ▄ ██▄█▀▄  █
███  █▀▄██▀▀▄▄▄█▄ █▄▀▄█▀ █▀█  ▄▄ █▀█▄██
█ ▀▄█▄▄▄▀█ ▀ ▄██▀██ █▀▄▀██▄  █ █▄█ ▀ ▄█
███▀ ▀█▄▀▄█▄▄▀▀▀█▄▄▄▀▄██▀█▄   █▄▀▄▄ ███
██▀▀▀██▄▀▄▀ ▄▀▀█▄█▄█▄█▄▀ █▄█▄▀▀█▄█▀▄▄ █
█▄▄ ▄▀ ▄▀██▄█▄█ ▄█▄ ▀ ██ ▀ ▀ █▄▄   ▄▀▄█
█▄█▀▄▄ ▄▀ ▄█ ▄█▀▀▀██▀▀█▀▀██ ▄▀  ▀█▀▄▄ █
█▀▀▄█▀ ▄█▀▄▄█▀  █▄█▄▄ ▄█▀ ██  ▀▄▀█▄█ ██
█ █▄ ▀▀▄ █▄▀█▀  ▄ ▄▄▀▀▄██▄▄█▄▄█▀ ▀    █
█▄██▄██▄█ █ █▄█▄ ▄█▀▀▄██▀█ ▄█ ▄▄▄ ▄ ▄▄█
█ ▄▄▄▄▄ █  █▀▄▄ ▄▄▄▄▄▀▄▀ ▄▄██ █▄█ ▀▄█ █
█ █   █ ██  ▄▀▀█▀  ▄▀▀██ ▄   ▄  ▄▄ ▄▀ █
█ █▄▄▄█ █▀ ██▀ ▄▄██ ▀▀█████▀█ ▄▀ █▀▄▄ █
█▄▄▄▄▄▄▄█▄▄█▄▄▄█▄██▄▄▄▄█▄▄███▄▄▄██▄██▄█

› Metro waiting on exp+ictiobiometria://expo-development-client/?url=http%3A%2F%2F10.0.0.105%3A8081
› Scan the QR code above with Expo Go (Android) or the Camera app (iOS)

› Press a │ open Android
› Press w │ open web

› Press r │ reload app
› Press m │ toggle menu
› Press d │ show developer tools
› shift+d │ toggle auto opening developer tools on startup (disabled)

› Press ? │ show all commands

Logs for your project will appear below. Press Ctrl+C to exit.
Started Metro Bundler
» android: block-permissions: No permissions provided
» android: block-permissions: No permissions provided
» android: block-permissions: No permissions provided
» android: block-permissions: No permissions provided
» android: block-permissions: No permissions provided
» android: block-permissions: No permissions provided
» android: block-permissions: No permissions provided
» android: block-permissions: No permissions provided
Android Bundling JavaScript [================================                                ] 49%

Not sure if it’s util, but these are the plugins I have declared on app.config.js

    "@react-native-firebase/app",
    "@react-native-firebase/crashlytics",
    "@react-native-firebase/perf",
    "@react-native-google-signin/google-signin",
    "expo-image-picker",
    "expo-location",

Also, this is something I’ve found now, having for example

android: {
    blockedPermissions: ["ACCESS_COARSE_LOCATION"],
    permissions: ["CAMERA", "ACCESS_FINE_LOCATION", "FOREGROUND_SERVICE"],
    ...
  },

will still trigger the warnings

@FatmaMahmoud698 just wait a bit for the next release.

Experiencing the same issue. I also notice it when I go to upload a build. When I build it in EAS - I will see the STDERR output of the same thing.