Bug 11474 - NSInvalidArgumentExceptionReason: Pushing the same view controller instance more than once is not supported
Summary: NSInvalidArgumentExceptionReason: Pushing the same view controller instance m...
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 6.3.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
Depends on:
Reported: 2013-03-29 10:25 UTC by Allie Miller
Modified: 2017-02-28 21:22 UTC (History)
5 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Allie Miller 2013-03-29 10:25:07 UTC
The following exception occurred after the update of Xamarin.iOS from MonoTouch/MonoDevelop:

Begin Exception MonoTouchException at 2013/03/27 22:46:23
Product: SkyDemon for iPad
MonoTouch: 6.2.0
MonoTouch.Foundation.MonoTouchException: Objective-C exception thrown. Name: NSInvalidArgumentExceptionReason: Pushing the same view controller instance more than once is not supported (<PlanningScreen: 0x4d9c260>)
at MonoTouch.UIKit.UINavigationController.PushViewController (MonoTouch.UIKit.UIViewController viewController, Boolean animated) [0x00000] in <filename unknown>:0
at Divelements.SkyDemon.RootScreen.DisplayEnvironment () [0x00000] in <filename unknown>:0
at Divelements.SkyDemon.RootScreen.InitiateSetup () [0x00000] in <filename unknown>:0
at Divelements.SkyDemon.RootScreen.OnChartManagerDone (System.Object sender, System.EventArgs e) [0x00000] in <filename unknown>:0
at Divelements.SkyDemon.Setup.ChartManagerScreen.OnDone (System.EventArgs e) [0x00000] in <filename unknown>:0
at Divelements.SkyDemon.Setup.ChartManagerScreen.ApplyChanges () [0x00000] in <filename unknown>:0
at Divelements.SkyDemon.Setup.ChartManagerScreen.OnApplyChangesClick (System.Object sender,System.EventArgs e) [0x00000] in <filename unknown>:0
at MonoTouch.UIKit.UIControlEventProxy.Activated () [0x00000] in <filename unknown>:0
at MonoTouch.UIKit.UIResponder.TouchesEnded (MonoTouch.Foundation.NSSet touches, MonoTouch.UIKit.UIEventevt) [0x00000] in <filename unknown>:0
at Divelements.SkyDemon.UI.SkdColorButton.TouchesEnded (MonoTouch.Foundation.NSSet touches,MonoTouch.UIKit.UIEvent evt) [0x00000] in <filename unknown>:0
at MonoTouch.UIKit.UIApplication.Main (System.String[] args, System.String principalClassName, System.StringdelegateClassName) [0x00000] in <filename unknown>:0
at Divelements.SkyDemon.Application.Main (System.String[] args) [0x00000] in <filename unknown>:0
End Exception
Comment 3 PJ 2013-11-19 16:44:46 UTC
This bug was targeted for a past milestone, moving to the next non-hotfix active milestone.
Comment 4 GouriKumari 2016-01-11 20:49:32 UTC
Moving this bug to future milestone. If the issue is happening with latest XI stable builds, please update the bug with info.
Comment 5 Vincent Dondain [MSFT] 2017-02-28 21:22:43 UTC
I would need a test case to know exactly what you're doing and to compare with a native sample.

Also this could have happened more frequently in the past due to slow animations (still happening?) and it's most likely not a Xamarin.iOS specific issue as I see other people on stack overflow hit the same issue with native code.




Closing this issue since I don't believe it's XI specific but feel free to reopen it it's still blocking / and you can provide us with a test case.