Nostros - why all these references to Google and Facebook in your error message

I am using Nostr and the Nostros app to get away from big tech.

On my degoogled phone when I try to send a message I get the error message below that includes a bunch references to Google and Facebook

What is going on?

type: crash
osVersion: google/panther/panther:13/TQ2A.230505.002/2023051600:user/release-keys
package: com.nostros:71003
process: com.nostros
processUptime: 29540 + 237 ms

com.facebook.react.common.JavascriptException: Invariant Violation: Tried to get frame for out of range index -1, js engine: hermes, stack:
invariant@1:105329
anonymous@1:491598
anonymous@1:491388
scrollToEnd@1:492165
scrollToEnd@1:482650
onFocus@1:3290381
handleFocus@1:2678513
_onFocus@1:593690
invokeGuardedCallbackImpl@1:315157
invokeGuardedCallback@1:315214
invokeGuardedCallbackAndCatchFirstError@1:315246
executeDispatch@1:315378
executeDispatchesAndReleaseTopLevel@1:319635
forEachAccumulated@1:316861
anonymous@1:319987
batchedUpdatesImpl@1:379177
batchedUpdates@1:319555
_receiveRootNodeIDEvent@1:319828
receiveEvent@1:373681
__callFunction@1:110673
anonymous@1:109025
__guard@1:109978
callFunctionReturnFlushedQueue@1:108983

	at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:72)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
	at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:188)
	at com.facebook.jni.NativeRunnable.run(Native Method)
	at android.os.Handler.handleCallback(Handler.java:942)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
	at android.os.Looper.loopOnce(Looper.java:201)
	at android.os.Looper.loop(Looper.java:288)
	at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:228)
	at java.lang.Thread.run(Thread.java:1012)

Sign in to add comment