eas-cli: Linking.addEventListener('url') won't fire when app is built with eas:build
After dealing with some issues related to uncommited files I’ve managed to build the app with eas:build but there are some weird things going on.
The most critical is that the app is not reacting after opened through a deeplink (which in our case means that our login flow is broken). To be clear: the app opens but my handler is not being fired. The weird thing is that the same app build with expo:build is working perfectly (link to the APKs below).
I also noticed that status bar behavior is different from one build to the other. Here’s the result with eas:build]
Here’s the (expected) result when build with expo:build:
Does anybody have a clue of what could that be?
Sorry for not preparing a clean reproducible demo but here’s our repo and our app.config.ts and the APKs:
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 20 (9 by maintainers)
@pdandradeb Did you find a way to trigger Linking.addEventListener(‘url’) with EAS build?
I had the exact same issue with
Linking.addEventListener('url')in our login flow, and used @brentvatne’s example to see what was the difference between a working setup and mine. The bit that i had to do to solve this was to addto my app.json, which was not required with
expo:build. I didn’t have to modify the existingintentFilterssetup.hope this helps