topic Re: Possible finger print login bug (android) in Arlo

Possible finger print login bug (android)

wtdnielsen — Mon, 17 Apr 2017 07:36:33 GMT

Hi I have just encountered a possible bug (or at least a very strange behaviour) in the Android app. I was logged in with my finger print login and when I tried to resume the app it behaved very slowly. I looked into the Logcat history and I copy-pasted the messages from the Arlo app to this GitHub gist:

https://gist.github.com/finneapps/5fad1981625b66ed2c0e27321b351cf1

notice how many times the following lines are repeated within a very short span of time:

04-17 09:00:19.075 4495-4495/? D/com.netgear.android.utils.AppSingleton: !!!!!!!!!!! Conection manager registered

04-17 09:00:19.078 4495-4495/? D/com.netgear.android.utils.AppSingleton: !!!!!!!!!!! Location manager registered

04-17 09:00:19.098 4495-4495/? D/com.netgear.android.utils.AppSingleton: https://arlo.netgear.com/hmsweb

04-17 09:00:19.103 4495-4495/? D/com.netgear.android.utils.AppSingleton: ===maxNavigationDate:20170430

04-17 09:00:19.150 4495-4495/? D/com.netgear.android.utils.AppSingleton: TRIM_MEMORY_RUNNING_LOW

04-17 09:00:19.191 4495-4495/? D/com.netgear.android.utils.VuezoneModel: Checking Data Model Integrity

04-17 09:00:19.191 4495-4495/? D/com.netgear.android.utils.VuezoneModel: Exiting System, bad data model!: userEmail:null bWasInsetup:false GetIsPureFriend():false

04-17 09:00:19.192 4495-4495/? E/com.netgear.android.utils.VuezoneModel: restarting app

04-17 09:00:19.215 5007-7594/? I/ActivityManager: Process com.netgear.android (pid 4495) has died

Could this be because the app expects an email, but it is missing because of finger print login?

The app runs into a loop where it keeps killing itself...

I will try to reproduce the error and come with even more details if possible

Re: Possible finger print login bug (android)

wtdnielsen — Mon, 17 Apr 2017 07:51:17 GMT

So it can be reproduced by having other memory consuming apps like Facebook running, and then open the app by clicking on the Notification that was created when motion has been detected.

notice that it runs into the restart app loop when it tried to open SplashActivity, but when it tries to open MainActivty the loop ends:

04-17 09:44:10.095 15706-15706/? D/com.netgear.android.main.MyLifecycleHandler: ============application activity created. onActivityCreated: com.netgear.android.activity.SplashActivity
04-17 09:44:10.096 15706-15706/? D/com.netgear.android.utils.VuezoneModel: Checking Data Model Integrity
04-17 09:44:10.096 15706-15706/? D/com.netgear.android.utils.VuezoneModel: Exiting System, bad data model!: userEmail:null bWasInsetup:false GetIsPureFriend():false
04-17 09:44:10.096 15706-15706/? E/com.netgear.android.utils.VuezoneModel: restarting app
04-17 09:44:10.118 5007-29407/? I/ActivityManager: Process com.netgear.android (pid 15706) has died
04-17 09:44:10.130 5007-29407/? I/ActivityManager: Start proc 15741:com.netgear.android/u0a221 for activity com.netgear.android/.main.MainActivity
04-17 09:44:10.252 15741-15741/? W/linker: /data/app/com.netgear.android-1/lib/arm/librealm-jni.so: is missing DT_SONAME will use basename as a replacement: "librealm-jni.so"
04-17 09:44:10.290 15741-15741/? D/com.netgear.android.utils.AppSingleton: !!!!!!!!!!! Conection manager registered
04-17 09:44:10.291 15741-15741/? D/com.netgear.android.utils.AppSingleton: !!!!!!!!!!! Location manager registered
04-17 09:44:10.296 15741-15741/? D/com.netgear.android.utils.AppSingleton: https://arlo.netgear.com/hmsweb
04-17 09:44:10.299 15741-15741/? D/com.netgear.android.utils.AppSingleton: ===maxNavigationDate:20170430
04-17 09:44:10.314 15741-15741/? D/com.netgear.android.utils.AppSingleton: TRIM_MEMORY_RUNNING_MODERATE
04-17 09:44:10.324 15741-15741/? D/com.netgear.android.main.MyLifecycleHandler: ============application activity created. onActivityCreated: com.netgear.android.main.MainActivity
04-17 09:44:10.326 15741-15741/? D/SwrveSDK: Using cache directory at /data/user/0/com.netgear.android/cache
04-17 09:44:10.751 5007-5007/? V/FingerprintService: startAuthentication(com.netgear.android)
04-17 09:44:10.751 5007-5007/? V/FingerprintService: starting client AuthenticationClient(com.netgear.android), initiatedByClient = true)
04-17 09:44:10.764 5007-5007/? W/FingerprintService: client com.netgear.android is authenticating...
04-17 09:44:10.882 15741-15741/? D/com.netgear.android.main.MyLifecycleHandler: ============application is visible. onActivityStarted: true activity:com.netgear.android.main.MainActivity
04-17 09:44:10.889 15741-15741/? D/com.netgear.android.communication.HttpApi: ====== Trying to subscribe to SSE events
04-17 09:44:10.889 15741-15741/? D/com.netgear.android.communication.HttpApi: ====== Failed to subscribe to SSE events, isSseForceUnsubscribed:false isSseSubscribed:false is Logged in:false
04-17 09:44:10.891 15741-15741/? D/com.netgear.android.main.MyLifecycleHandler: ============application is in foreground. onActivityResumed: true activity:com.netgear.android.main.MainActivity
04-17 09:44:10.900 15741-15741/? D/com.netgear.android.utils.ConnectionChangeReceiver: !!!!!!!!!!!!!!Connectivity Changed. Extras key[networkInfo]=[type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: "ZyXEL0C0DC8", failover: false, available: true, roaming: false, metered: false]
04-17 09:44:10.900 15741-15741/? D/com.netgear.android.utils.ConnectionChangeReceiver: !!!!!!!!!!!!!!Connectivity Changed. Extras key[networkType]=1
04-17 09:44:10.900 15741-15741/? D/com.netgear.android.utils.ConnectionChangeReceiver: !!!!!!!!!!!!!!Connectivity Changed. Extras key[inetCondition]=100
04-17 09:44:10.901 15741-15741/? D/com.netgear.android.utils.ConnectionChangeReceiver: !!!!!!!!!!!!!!Connectivity Changed. Extras key[extraInfo]="ZyXEL0C0DC8"
04-17 09:44:11.166 5007-5075/? I/ActivityManager: Displayed com.netgear.android/.main.MainActivity: +1s47ms (total +6s505ms)

Re: Possible finger print login bug (android)

jguerdat — Mon, 17 Apr 2017 12:20:32 GMT

Opening a case with support would potentially get your data to the engineers.

Re: Possible finger print login bug (android)

JamesC — Mon, 24 Apr 2017 15:32:57 GMT

wtdnielsen,

I agree with jguerdat's post above, open a case with the Arlo Support Team to further investigate. Feel free to private message me with the case number and I will monitor your case.

JamesC

Re: Possible finger print login bug (android)

wtdnielsen — Tue, 25 Apr 2017 06:26:51 GMT

I have opened a case. I actual found another serious issue with the Android app that I also included in the case. I really hope the app will be improved. Last week, in the middle of the night, Arlo warned me about two guys trying to break in to my house, so Arlo saved me for having two guys inside my house while I was sleeping! So in that sense I am happy, but still the app need some more love.