Answers

• JohnHardman GBUniversity admin

  November 2017

  @JassimRahma said:
  Why my iOS simulator crashes?

  @JassimRahma -

  (1) Your app crashes when running in the simulator, or the simulator crashes?
  (2) Reword "crashes" as "throws an unhandled exception". Have you got any details of the exception?

  0
• JassimRahma USMember ✭✭✭✭

  November 2017

  Sorry, my app crashes when it starts on iOS simulator but perfectly working on Android emulator.

  The log doesn't show any exception..

  How to troubleshoot it here?

  0
• JassimRahma USMember ✭✭✭✭

  November 2017

  Oh Ok I got it but still need help..

  It crashes because I have:

  OneSignal.Current.StartInit("xxxxxxx-xxxxx-xxxxx-xxxxx-xxxxxx")
     .EndInit();
  

  in App.xaml.cs and AppDelegate.cs

  If I comment it then the simulator will work fine

  WHat's the solution other than commenting it?

  0
• JohnHardman GBUniversity admin

  November 2017

  @JassimRahma - "crash" = "unhandled exception". If you know where the exception is being thrown, put an exception handler around it to get the details of the exception.

  Have you followed the iOS and iOS simulator instructions at https://documentation.onesignal.com/v3.0/docs/xamarin-sdk-setup ?

  0
• JassimRahma USMember ✭✭✭✭

  November 2017 edited November 2017

  What I mean is if I use this:

  OneSignal.Current.StartInit("xxxxxxx-xxxxx-xxxxx-xxxxx-xxxxxx")
     .EndInit();
  

  in the Simulator it will crash but not on real device..

  So is there any way to say

  fi (**NOT RUNNING ON SIMULATOR**)
  {
       OneSignal.Current.StartInit("xxxxxxx-xxxxx-xxxxx-xxxxx-xxxxxx")
            .EndInit();
  }
  

  0
• Amar_Bait DZMember ✭✭✭✭✭

  November 2017

  http://lmgtfy.com/?q=how+to+detect+ios+simulator+Xamarin+c#

  1
• JohnHardman GBUniversity admin

  November 2017 Accepted Answer

  @JassimRahma

  The question has transitioned through:

  (1) Why my iOS simulator crashes?
  (2) How to troubleshoot it here?
  (3) So is there any way to say "fi (NOT RUNNING ON SIMULATOR)"

  IMHO, it would be better to investigate (1) and (2) before making use of (3). Assuming the line of code highlighted is where the exception is being raised - what would your app do if that line of code threw an exception (perhaps for a different reason) on a physical device? If it happened in development, how would you troubleshoot it? If it happened in production, how would you troubleshoot it? By jumping to (3) before answering (1) and (2), you have technical debt building up.

  @nadjib - The most stylish way of advising somebody to use Google that I have seen so far :-)

  5
• Amar_Bait DZMember ✭✭✭✭✭

  November 2017 edited November 2017

  @JohnHardman learned it from XDA forums, from the time I was doing some game development. And believe me, these Forums are way better than XDA/game engines one. I mean during that period, we had literally questions like "I'm 13 years old, never coded in my life, but I know how to resolve 2nd degree equations. I want to make a game like God of War, but in better since it'll be a collaborative MMO hack and slash with 1 million concurrent users. Can you show me, or do it and give you 20% of profits."

  0