Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

[Android]App Crashes randomly with NavigationPageRenderer.UpdateToolbar error #4708

Open
niraj-bpsoftware opened this issue Dec 11, 2018 · 3 comments
Labels
e/10:clock10: 10 help wanted We welcome community contributions to any issue, but these might be a good place to start! i/high Completely doesn't work, crashes, or is unusably slow, has no obvious workaround; occurs less often inactive Issue is older than 6 months and needs to be retested p/Android t/bug 🐛 up-for-grabs We welcome community contributions to any issue, but these might be a good place to start!

Comments

@niraj-bpsoftware
Copy link

Description

We have a reoccurring bug in the app over the past month that we are struggling to get to the bottom of, It’s in android only.

This error occurs randomly if you close the app, then open it up again after some time – hours / days. We have not found a reliable we to constantly reproduce this error, but we are getting it regularly, (once to twice a day).
It appears something is going wrong with the bootup process. The problem is very hard to reliably reproduce it appears to occur 1 to 3 seconds after a book. It doesn’t happen in debug mode, we can only trace the problem through the App Centre analytics.

The error is :
NavigationPageRenderer.UpdateToolbar ()
NavigationPageRenderer.OnAttachedToWindow ()
View.n_OnAttachedToWindow (System.IntPtr jnienv, System.IntPtr native__this)
(wrapper dynamic-method) System.Object.42(intptr,intptr)

Steps to Reproduce

  1. Login to App.
  2. Close the App
  3. Open after some time (may be 30 minutes).
    report-2518577414087959999-a4dd2419-076f-4b2d-94e0-6dfe7273d405.txt

Expected Behavior

App shouldn't crash.

Actual Behavior

App crashes randomly on load.

Basic Information

  • Version with issue: Xamarin Forms 3.4.0.1008975
  • Last known good version: NA
  • IDE: 15.8.7
  • Platform Target Frameworks:
    • Android: 7.0
    • Android Build: NRD90M
  • Android Support Library Version:
  • Nuget Packages: ReactiveUi 9.4.1, System.Reactive 4.1.2
  • Affected Devices: Android devices
@hartez
Copy link
Contributor

hartez commented Dec 11, 2018

@niraj-bpsoftware Are you using MvvmCross in your application?

@hartez hartez added the s/needs-info ❓ A question has been asked that requires an answer before work can continue on this issue. label Dec 11, 2018
@niraj-bpsoftware
Copy link
Author

Hi @hartez ,
Thank you for checking this.
we are using MvvmCross.Platform 5.7.0 and MvvmCross.Plauglin.Ble 1.3.0 for Bluetooth functionality.
Thanks.

@hartez hartez removed the s/needs-info ❓ A question has been asked that requires an answer before work can continue on this issue. label Dec 11, 2018
@samhouts samhouts added the i/high Completely doesn't work, crashes, or is unusably slow, has no obvious workaround; occurs less often label May 29, 2019
@samhouts samhouts added inactive Issue is older than 6 months and needs to be retested help-wanted up-for-grabs We welcome community contributions to any issue, but these might be a good place to start! help wanted We welcome community contributions to any issue, but these might be a good place to start! and removed help-wanted labels Jun 25, 2019
@samhouts samhouts added this to the 5.0.0 milestone Aug 13, 2020
@samhouts samhouts removed this from the 5.0.0 milestone Nov 2, 2020
@filipnavara
Copy link
Contributor

This can be reproduced quite reliably with the "don't keep activities" developer option. In our case we also had to combine it with launching the app with intent after the activity was destroyed (eg. through shortcut or a notification). The crash seems to happen because activity.SupportActionBar == null.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
e/10:clock10: 10 help wanted We welcome community contributions to any issue, but these might be a good place to start! i/high Completely doesn't work, crashes, or is unusably slow, has no obvious workaround; occurs less often inactive Issue is older than 6 months and needs to be retested p/Android t/bug 🐛 up-for-grabs We welcome community contributions to any issue, but these might be a good place to start!
Projects
None yet
Development

No branches or pull requests

5 participants