5 Answer(s)

• 

  0

  alper created 4 years ago

  Support Team

  don't use WebRequestExecuter in AppDelegate.cs and use it as is.

  Save Cancel
• 

  0

  Jorahealth created 4 years ago

  Thank you @alper

  We are tried with commenting the the codes which use WebRequestExecuter directly in AppDelegate.cs class.** But it did not work. ** On Further investigation we understand that When we work with FCM, the code in AppDelegate.cs class "ApplicationBootstrapper.InitializeIfNeeds<DecisivelyXamarinIosModule>();" calling the method "userConfigurationService.GetAsync(AccessTokenManager.IsUserLoggedIn)". And retuns null as result in Decisively.ViewModels.Base.UserConfigurationManager.cs class. And it throwing null object reference exception and calling App.ExitApplication(); method.

  Without FCM integration code it works perfectly and got result.

  

  Save Cancel
• 

  0

  alper created 4 years ago

  Support Team

  In AppDelegate.cs class there's no call to UserConfigurationManager.GetAsync()

  

  this code

   ApplicationBootstrapper.InitializeIfNeeds<AbpZeroTemplateXamarinIosModule>();
  

  runs the below

  
   if (IsInitialized)
              {
                  return;
              }
  
              AbpBootstrapper = AbpBootstrapper.Create<T>(options =>
              {
                  //Interceptors (dynamic proxying) are not supported in IOS platform. Also, it's not needed on the client side.
                  options.DisableAllInterceptors = true;
              });
  
              AbpBootstrapper.IocManager.IocContainer.AddFacility<LoggingFacility>(f =>
              {
                  f.LogUsing<TraceLoggerFactory>();
              });
  
              AbpBootstrapper.Initialize();
  

  Save Cancel
• 

  0

  Jorahealth created 4 years ago

  Yes you are right, there is no call to UserConfigurationManager.GetAsync() in AppDelegate.cs. On the further investigation we found that UserConfigurationManager.GetAsync() method is calling from App.Xamal.cs file. And it returns reult as null.

  So to solve this issue, we did some code modifications in AppDelegate.cs

  1. Removed delay from RegisterForRemoteNotifications() method
  2. Added a 30 seconds delay before calling return base.FinishedLaunching(app, options); in FinishedLaunching() method.

  The app then works perfectly and got expected result for UserConfigurationManager.GetAsync() method. Also received FCM test notification too.

  **Is this the best way to solve this? **

  

  Save Cancel
• 

  0

  alper created 4 years ago

  Support Team

  this is a solution but if there's a callback method RegisterForRemoteNotifications() method, you can call FinishLaunching in there. Otherwise 3 sec maybe issue when using slow networks.

  Save Cancel