Cannot access a disposed object
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, csharp
- Domain
- mobile-dev
Research direction
Start by inspecting NotificationBuilder.TimerFinished and the Notify timer callback shown in the stack trace. Reproduce the failure on the reported Android environment if possible, then verify that the notification cancellation path no longer accesses a disposed Android.App.NotificationManager.
Written by the indexing model from the issue text.
Description
This is on a Xamarin Forms app.
Android: 9
Android Build: PKQ1.190118.001
Manufacturer: vivo
Model: vivo 1727
Xamarin Exception Stack:
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'Android.App.NotificationManager'.
at Java.Interop.JniPeerMembers.AssertSelf (Java.Interop.IJavaPeerable self) [0x00029] in <4d2af34ca2694c37a4ea3d8074f2f66b>:0
at Java.Interop.JniPeerMembers+JniInstanceMethods.InvokeVirtualVoidMethod (System.String encodedMember, Java.Interop.IJavaPeerable self, Java.Interop.JniArgumentValue* parameters) [0x00000] in <4d2af34ca2694c37a4ea3d8074f2f66b>:0
at Android.App.NotificationManager.Cancel (System.Int32 id) [0x00022] in <519a5f3aaae444f4b50cf623ff03eb78>:0
at Plugin.Toasts.NotificationBuilder.TimerFinished (System.String id, System.Boolean cancel, System.Boolean allowTapInNotificationCenter) [0x00028] in <ff2bac5dfa8f470a8c69cfd33f67eef9>:0
at Plugin.Toasts.NotificationBuilder+<>c__DisplayClass23_1.<Notify>b__0 (System.Object x) [0x00031] in <ff2bac5dfa8f470a8c69cfd33f67eef9>:0
at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <254b242c97154351aae8e0970082105e>:0
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00008] in <254b242c97154351aae8e0970082105e>:0
at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <254b242c97154351aae8e0970082105e>:0
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <254b242c97154351aae8e0970082105e>:0
- Dominant language
- C#
- Stars
- 275
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EgorBo/Toasts.Forms.Plugin
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
EgorBo/Toasts.Forms.Plugin#182 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
EgorBo/Toasts.Forms.Plugin#181 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
EgorBo/Toasts.Forms.Plugin#180 · 2 comments ·
-
MacOS supportOpen
Difficulty 5/5 Over a week Newbie friendliness 18/100
EgorBo/Toasts.Forms.Plugin#178 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
EgorBo/Toasts.Forms.Plugin#176 · 2 comments ·
All issues in EgorBo/Toasts.Forms.Plugin
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
ready-for-agent size:S status:todo
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
elsa-workflows/elsa-foundation#2830 ·
Maintainers usually reply within 1 day
-
Review - Maintainer WG-Maintainers-Build
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
PowerShell/PowerShell#28220 · 1 comment ·
Maintainers usually reply within 1 day
-
area: docs eco: dotnet good first issue help wanted lane: free-agent roadmap size: XS type: docs
Difficulty 2/5 Under an hour Newbie friendliness 72/100
arminazimi/evergreen#377 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day