search

digidem / comapeo-mobile

The next version of Mapeo mobile
GNU General Public License v3.0
5 stars 1 forks source link

Cryptic deserialization error after accepting invite #364

Closed achou11 closed 3 months ago

achou11 commented 3 months ago

Have very little idea of the cause of this. Guess is that some API call is returning an error instance, which RPC reflector (or React Native) can't deserialize?

only tried this in development

image
achou11 commented 3 months ago

Context from Gregor:

The error is coming from RPC reflector, so you are not able to see the actual error. If you look at the earlier thread in the SWM I explain to SWM why this is happening because of the metro config. There is a setting in metro config that tells it to not resolve dependencies correctly, so deps are resolved with incorrect versions. I think they have done this because the bundled was maybe trying to bundle the backend code. I would think the solution is to blocklist the backend folder in metro config - see Mapeo-mobile for the config options. The current metro config in comapeo will cause weird bugs if it’s not changed.

Will fix the deserialization part, but not the underlying error

achou11 commented 3 months ago

Closing this for now since the PR to fix tge deserialization error has been merged. there might be an error at the app level that needs fixing, but will create a separate issue if needed