Warnings with create-expo-app@latest

[aramir]

Minimal reproducible example

npx create-expo-app@latest test-app && cd test-app && npm install && npm run web

Steps to reproduce

Currently creating an app with create-expo-app as per tutorial:

npx create-expo-app@latest StickerSmash
cd StickerSmash
npm install
npm run web

results in the following warnings in console:

WARN  "shadow*" style props are deprecated. Use "boxShadow". 
...
WARN  props.pointerEvents is deprecated. Use style.pointerEvents 

Both were previously reported in the following issues:

• expo router entry.js props.pointerEvents is deprecated. Use style.pointerEvents #33290
• Getting warning "shadow*" style props are deprecated. Use "boxShadow" for expo-web in nx-workspace without webpack. react-navigation/react-navigation#11730

(Issues seem to be closed as stale)

The warnings seem benign, however getting cryptic warnings from the basic tutorial scaffolding setup is probably not the best possible impression.

Environment

expo-env-info 1.3.4 environment info:
System:
  OS: Windows 10 10.0.19045
Binaries:
  Node: 22.17.0 - C:\Program Files\nodejs\node.EXE
  Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
  npm: 11.4.2 - C:\Program Files\nodejs\npm.CMD
npmPackages:
  expo: ~53.0.17 => 53.0.19
  expo-router: ~5.1.3 => 5.1.3
  react: 19.0.0 => 19.0.0
  react-dom: 19.0.0 => 19.0.0
  react-native: 0.79.5 => 0.79.5
  react-native-web: ~0.20.0 => 0.20.0
Expo Workflow: managed

Expo Doctor Diagnostics

expo-doctor@1.13.5
Ok to proceed? (y) y

15/15 checks passed. No issues detected!

[wonghin]

I also meet this issue recently

[wonghin]

I solved this issue by removing using Flipper.
Reference: https://github.com/expo/expo/issues/25508#issuecomment-1868054363

@aramir

[aramir]

Nope, not using it

[niquedegraaff]

The warnings seem benign, however getting cryptic warnings from the basic tutorial scaffolding setup is probably not the best possible impression.

This is the most important phrase.
New people are going to have not the best impression of Expo if the freaking basic tut already throws warnings like this.

[expo-bot]

Thank you for filing this issue!
This comment acknowledges we believe this may be a bug and there’s enough information to investigate it.
However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.

[hirbod]

The boxShadow warning is already resolved in main and will be shipped with the next Expo Router version. (You can install the canary if you want to test it.)

We prepared a fix for the pointerEvents that is caused upstream by react-navigation. Before react-navigation can merge the change, a PRs in react-native-testing-library and react-native-web need to be merged.