Resources$NotFoundException On Google Robo Test

[NickIliev]

From @NickIliev on March 16, 2018 6:34

From @rakeshgirase on March 15, 2018 21:42

Please, provide the details below:

Did you verify this is a real problem by searching the [NativeScript Forum]

Yes

Tell us about the problem

One out of 10 devices which were under test encountered following exception and I felt like not leaving it this time as I got a logs of the same.
logcat.txt
Though there is nothing specific, I have attached the video of the test which gave this exception:
Video: https://drive.google.com/open?id=1uiGHhPdT8LhQ83HMlczgrY-w5FRFkn5n
Following is stacktrace:

03-14 23:11:59.425: I/Robo(14384): android.content.res.Resources$NotFoundException: Resource ID #0xffffffec
03-14 23:11:59.425: I/Robo(14384): 	at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:255)
03-14 23:11:59.425: I/Robo(14384): 	at android.content.res.Resources.loadXmlResourceParser(Resources.java:2187)
03-14 23:11:59.425: I/Robo(14384): 	at android.content.res.Resources.getAnimation(Resources.java:1202)
03-14 23:11:59.425: I/Robo(14384): 	at android.animation.AnimatorInflater.loadAnimator(AnimatorInflater.java:127)
03-14 23:11:59.425: I/Robo(14384): 	at android.animation.AnimatorInflater.loadAnimator(AnimatorInflater.java:108)
03-14 23:11:59.425: I/Robo(14384): 	at android.animation.AnimatorInflater.loadAnimator(AnimatorInflater.java:93)
03-14 23:11:59.425: I/Robo(14384): 	at android.app.FragmentManagerImpl.loadAnimator(FragmentManager.java:828)
03-14 23:11:59.425: I/Robo(14384): 	at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1072)
03-14 23:11:59.425: I/Robo(14384): 	at android.app.FragmentManagerImpl.removeFragment(FragmentManager.java:1283)
03-14 23:11:59.425: I/Robo(14384): 	at android.app.BackStackRecord.run(BackStackRecord.java:766)
03-14 23:11:59.425: I/Robo(14384): 	at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1585)
03-14 23:11:59.425: I/Robo(14384): 	at android.app.FragmentManagerImpl$1.run(FragmentManager.java:484)
03-14 23:11:59.425: I/Robo(14384): 	at android.os.Handler.handleCallback(Handler.java:755)
03-14 23:11:59.425: I/Robo(14384): 	at android.os.Handler.dispatchMessage(Handler.java:95)
03-14 23:11:59.425: I/Robo(14384): 	at android.support.test.espresso.base.Interrogator.loopAndInterrogate(Interrogator.java:148)
03-14 23:11:59.425: I/Robo(14384): 	at android.support.test.espresso.base.UiControllerImpl.loopUntil(UiControllerImpl.java:465)

Which platform(s) does your issue occur on?

Android

Please provide the following version numbers that your issue occurs with:

• CLI: (run tns --version to fetch it)
• Cross-platform modules: (check the 'version' attribute in the
  node_modules/tns-core-modules/package.json file in your project)
• Runtime(s): (look for the "tns-android" and "tns-ios" properties in the
  package.json file of your project)
• Plugin(s): (look for the version number in the package.json file of your
  project)
  The complete project can be found at https://github.com/rakeshgirase/QSB.

Please tell us how to recreate the issue in as much detail as possible.

The best approach would be to get your code running in the NativeScript Playground and share the link with us, along with any additional details or steps to reproduce needed for examining the issue there.

Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.

I understand that it is an issue which is difficult to pin point and fix.. Its strange that code works just fine on 9 out of 10 devices. However, if at all code is required then you can find it https://github.com/rakeshgirase/QSB

Copied from original issue: #5549

Copied from original issue: NativeScript/android#974

[NickIliev]

From @sserdyuk on March 22, 2018 18:48

@NickIliev I'd like to add my two cents here.

First, I do have the same reports from the pre-launch testing in Firebase Test Lab. I get these consistently since Google implemented "more comprehensive pre-launch report" that "now explores your app even more deeply and may find more crashes". All quoted text is Google's.

I get 2-3 reports for each build. Here's a graph of issues since January 18th 2018. See graphs and screenshots below.

Second, more importantly, this is not only happening during robo testing in the lab, I also have a similar crash report from the real production use.

From what I can see in the videos, it seems to be related to user action during or right after navigating back. I use topmost().goBack(); to return from the list of categories, and that's about where it's crashing.

I can actually recreate it on my phone by tapping while transitions are happening, similar to how the robo testers do it in the videos.

I think this deserves a high priority ticket, and I'd be happy to help solve the issue.

$ tns info
All NativeScript components versions information
┌──────────────────┬─────────────────┬────────────────┬─────────────┐
│ Component        │ Current version │ Latest version │ Information │
│ nativescript     │ 3.4.3           │ 3.4.3          │ Up to date  │
│ tns-core-modules │ 3.4.1           │ 3.4.1          │ Up to date  │
│ tns-android      │ 3.4.2           │ 3.4.2          │ Up to date  │
│ tns-ios          │ 3.4.1           │ 3.4.1          │ Up to date  │
└──────────────────┴─────────────────┴────────────────┴─────────────┘

Please note the logcat files and videos from the Test Lab below:

logcat (2).txt
screen video (2)

logcat (1).txt
screen video (1)

logcat.txt
screen video

Firebase Crash Reporting for production app:

Pre-launch testing in Firebase Test Lab:

[NickIliev]

From @sserdyuk on April 2, 2018 21:14

@NickIliev Did you see my comment that it is also happening in production? Is that not a concern? It's been 11 days and there's no activity here.

[NickIliev]

From @Plamen5kov on April 3, 2018 7:3

Hi @sserdyuk
I tried to reproduce the issues you're facing but without steps to reproduce, It's going to be really difficult to help you.
Can you provide us with some sample repo that has better odds of crashing?

[NickIliev]

From @sserdyuk on April 3, 2018 15:26

@Plamen5kov Here's logcat from a real device I just recreated it on. I added verbose logging per your instructions in the other issue.

log1.txt

declare function __enableVerboseLogging()
__enableVerboseLogging()

[NickIliev]

From @etabakov on April 10, 2018 13:39

@sserdyuk I was able to reproduce the issue using your project and we are currently looking for the reason. I will get back when we have any update.

[NickIliev]

From @sserdyuk on April 10, 2018 13:59

@etabakov Terrific. Thank you!

[NickIliev]

From @etabakov on April 11, 2018 13:9

After some investigation it looks like the problem is related to multiple slide transitions trying to be executed simultaneously and asynchronously.

[NickIliev]

The issue might be possibly reproduced via this action

Another possibility to reproduce the issue is to navigate fast via the custom tabs items which again causes similar crash - details and sample app logged here

Reproducible via https://github.com/NickIliev/NS-Issues-2018-II/tree/master/test/tabCrashAndroidRes
Removing the transition or lowering the transition duration seems to resolve the case

Also see the detailed observations and explanation made by @DickSmith here and by @NathanaelA here related to this issue

[DickSmith]

Just as a further clarification, this issue can be experienced on most/all devices/makes/models, include all major versions of the Samsung Galaxy S-series (the most popular available).

[vakrilov]

@DickSmith
This issue look really similar to #6199 which was addressed with this PR: #6275
Closing this one as the PR should heal the problem.

[lock]

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