Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2021-06-08

Channels

#cljsrn
<
2021-06-08
>
pez09:06:35

I’ve run into this strange issue that some changes I’ve made cause the Android version of the app to sometimes turn almost completely unresponsive. All I can do is scroll the current view. No buttons work, including tabs. Also the REPL “disappears” shadow-cljs says “No JS Runtime”. Anyone know of some adb commands I can run to try see what (if anything) is going on on the phone? Or even recognize the condition. I’m completely clueless…

dotemacs09:06:11

adb logcat ?

pez09:06:16

Thanks! When I try that I see that things happen at some layer when I tap things: 

06-08 11:22:31.569   874  1304 I InputDispatcher: Delivering touch to (11875): action: 0x1, toolType: 0
06-08 11:22:31.569 11875 11875 D ViewRootImpl: ViewPostImeInputStage processPointer 1
06-08 11:22:31.849   874  4103 D SSRM:n  : SIOP:: AP = 360, PST = 360, CUR = 450, LCD = 160
06-08 11:22:33.519   874  1304 I InputDispatcher: Delivering touch to (1389): action: 0x4, toolType: 0
06-08 11:22:33.519   874  1304 I InputDispatcher: Delivering touch to (11875): action: 0x0, toolType: 0
06-08 11:22:33.529 11875 11875 D ViewRootImpl: ViewPostImeInputStage processPointer 0
06-08 11:22:33.529   874  1304 D PowerManagerService: [api] userActivityFromNative : 240 (event: 2 flags: 0) eventTime = 654302544
06-08 11:22:33.609   874  1304 I InputDispatcher: Delivering touch to (11875): action: 0x1, toolType: 0
06-08 11:22:33.609 11875 11875 D ViewRootImpl: ViewPostImeInputStage processPointer 1
06-08 11:22:34.949   874  1999 E Watchdog: !@Sync 21798 [06-08 11:22:34.960]
06-08 11:22:35.579   874  1304 I InputDispatcher: Delivering touch to (1389): action: 0x4, toolType: 0
06-08 11:22:35.579   874  1304 I InputDispatcher: Delivering touch to (11875): action: 0x0, toolType: 0
06-08 11:22:35.579 11875 11875 D ViewRootImpl: ViewPostImeInputStage processPointer 0
06-08 11:22:35.659   874  1304 I InputDispatcher: Delivering touch to (11875): action: 0x1, toolType: 0
06-08 11:22:35.659 11875 11875 D ViewRootImpl: ViewPostImeInputStage processPointer 1
06-08 11:22:36.399   874  1304 I InputDispatcher: Delivering touch to (1389): action: 0x4, toolType: 0
06-08 11:22:36.399   874  1304 I InputDispatcher: Delivering touch to (11875): action: 0x0, toolType: 0
06-08 11:22:36.399 11875 11875 D ViewRootImpl: ViewPostImeInputStage processPointer 0
06-08 11:22:36.479   874  1304 I InputDispatcher: Delivering touch to (11875): action: 0x1, toolType: 0
06-08 11:22:36.489 11875 11875 D ViewRootImpl: ViewPostImeInputStage processPointer 1
06-08 11:22:37.299   874  1304 I InputDispatcher: Delivering touch to (1389): action: 0x4, toolType: 0
06-08 11:22:37.299   874  1304 I InputDispatcher: Delivering touch to (11875): action: 0x0, toolType: 0
06-08 11:22:37.299 11875 11875 D ViewRootImpl: ViewPostImeInputStage processPointer 0
06-08 11:22:37.359   874  1304 I InputDispatcher: Delivering touch to (11875): action: 0x1, toolType: 0
06-08 11:22:37.359 11875 11875 D ViewRootImpl: ViewPostImeInputStage processPointer 1

thheller09:06:46

react-native log-android? (or whatever the command was for getting console.log logs)

pez09:06:57

That was the command. 😃

pez09:06:37

However, nothing is logged, which I guess tells me something…

thheller09:06:34

hmm yeah no idea how to debug RN stuff either. maybe you added an infitie loop or so?

pez09:06:06

I shouldn’t have (not ruling it out). It only happens on Android which is extra strange.

pez12:06:53

It seems I am running into this issue https://github.com/software-mansion/react-native-reanimated/issues/654 and that the fix is to upgrade react native and react navigation….

raspasov22:06:51

@U0ETXRFEW Which version of RN are you on?

raspasov00:06:13

That’s actually not too old. Sorry, I haven’t tried Android in a while so I can’t offer much help.

raspasov00:06:23

Did you manage to get it working?

pez07:06:10

Thanks for asking! I think I might have managed to not provoke it in the release build by removing some transition animations. It makes the app less lovely, and also it still happens on reload of the dev app making my Android development workflow painful. So, no, haven’t really got it working.

pez07:06:04

The RN version we use is old enough to make upgrading from it to something modern really hard. We have a branch where we are using RN 64, and this lock-up problem is gone there. But there are quite a lot of other problems, one of which is that the Android app is super slow and not really usable…

pez09:06:10

On a brighter note. Have you tried Vysor? It is wonderful for Android. It perfectly mirrors the phone screen and I can use either my Mac or the phone to operate it. Even typing on the keyboard.

👍 2
dotemacs09:06:57

I just wish that it didn’t require cable connection from the machine to the phone. But I guess it uncovers a bigger issue, the quality of the Android emulator, especially when compared with what  has. I remember ten years ago there was a saying “Google hates developers” in the context of the quality/UX of the mobile emulator. And today, it’s like nobody cares at Google.

pez09:06:12

Yes, the emulator is pretty horrible. Vysor makes it nice to develop for Android. 😃