Cannot open Hermes JS Debugger on adding metro-config package to address - "metro-file-map: Haste module naming collision" due to amplify/#current-cloud-backend having same files as amplify/backend. #12245
Labels
Expo
For issues where expo is in use
investigating
This issue is being investigated
React Native
React Native related issue
Before opening, please confirm:
JavaScript Framework
React Native
Amplify APIs
Not applicable
Amplify Categories
Not applicable
Environment information
Describe the bug
Getting the below error on
npx expo start
So to fix it, adding metro-config(version 0.79.1) will fix the issue but will prevent Hermes JS Debugger from launching the debugger as there is nothing published in /json/list
Below is what is returned when amplify is NOT used the /json/list returns the list of debuggable apps
Working - http://192.168.29.8:8081/json/list
Expected behavior
Should ignore the amplify/#current-cloud-backend and js debugger should get launched
Reproduction steps
yarn create expo-app AwesomeProject
npx expo start
metro-file-map: Haste module naming collision: wildAuthPostConfirmation
as mentioned above.Haste module naming collision
)FetchError: invalid json response body at http://192.168.29.218:8081/json/list reason: Unexpected token < in JSON at position 0
andCode Snippet
// Put your code below this line.
Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: