Skip to content
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

abi37_0_0.com.facebook.react.bridge.ReadableNativeMap cannot be cast to java.lang.String #8130

Closed
hmellor opened this issue May 3, 2020 · 9 comments
Labels
needs more info To be used when awaiting reporter response stale

Comments

@hmellor
Copy link

hmellor commented May 3, 2020

🐛 Bug Report

Environment

Expo CLI 3.20.1 environment info:
System:
OS: Windows 10 10.0.18363
Binaries:
Node: 10.16.0 - C:\Program Files\nodejs\node.EXE
npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
npmPackages:
expo: ^37.0.8 => 37.0.8
react: 16.9.0 => 16.9.0
react-dom: 16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4
react-navigation: ^4.1.0 => 4.3.8

Targeting both Android and IOS

Steps to Reproduce

Using the atob workaround to use Firebase Firestore I am able to interact with Firestore. But after using the app for a short time afterwards the app crashes (length of time varies).

Expected Behavior

App should not crash

Actual Behavior

The app crashes with the following error on the device:

abi37_0_0.com.facebook.react.bridge.ReadableNativeMap cannot be cast to java.lang.String
@sjchmiela
Copy link
Contributor

Hey @hmellor, I'm sorry you experience this bug. Do you have any more error information coming from the crash? The cannot be cast is a generic bug and it's difficult to guess where it's coming from. If you had a stacktrace that would be extremely helpful!

@hmellor
Copy link
Author

hmellor commented May 4, 2020

The only place I can see any detail on the error is on the device itself:
Screenshot_20200504-142524_Expo

@sjchmiela
Copy link
Contributor

Hm, unfortunately this looks like a native problem and to debug it we'll need a native stacktrace. Do you feel comfortable using Android Studio? It includes the logcat tool which should make it easy to find the stacktrace — https://developer.android.com/studio/debug/am-logcat

If not, would you be able to provide us with a Snack reproducing the issue?

@hmellor
Copy link
Author

hmellor commented May 4, 2020

Unfortunately I think I'd need to give you access to a Firebase Firestore to make a useful Snack. I'll try Android Studio and get back to you. Thanks

@byCedric byCedric added the needs more info To be used when awaiting reporter response label May 4, 2020
@banjianpan
Copy link

Did anyone figure this out? or is this problem fixed?

@banjianpan
Copy link

I currently also experiencing this problem. When accessing my firestore, after about 1 minute and 7 seconds, I get the same error as above

@stale
Copy link

stale bot commented Sep 14, 2020

It's been a while since we've had any activity on this issue, and seeing as it needs more info before we can properly address it, we will be closing it in one month. If you've found a fix, please share it! Otherwise, please provide the info we asked for, especially a reproducible example. Thanks!

@stale stale bot added the stale label Sep 14, 2020
@stale
Copy link

stale bot commented Oct 15, 2020

This issue has been automatically closed since there has not been any recent activity after it was marked as stale. Please open a new issue for any related bugs.

@stale stale bot closed this as completed Oct 15, 2020
@sjchmiela
Copy link
Contributor

FWIW it looks like newer releases of Firebase should have this issue fixed — firebase/firebase-js-sdk#2667 🥳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more info To be used when awaiting reporter response stale
Projects
None yet
Development

No branches or pull requests

5 participants