AppContext null and ConfigurationManager not initialized in device logs

Products

• CA Mobile API Gateway

Issue/Introduction

After Upgrading the mobile app using the MAG SDK 2.3.0 instead of 2.1.0 we  began to see the error below.

|<<<[MAS]>>>|                    E  | ConfigurationManager:167 | load() | >>> appContext is null.

|<<<[MAS]>>>|                    W  | StorageProvider:46 | getInstance() | >>> ConfigurationManager not initialized.

|<<<[MAS]>>>|                    E  | MobileSsoFactory:214 | reset() | >>> ConfigurationManager not initialized.

                                                             java.lang.IllegalStateException: ConfigurationManager not initialized.

                                                                        at com.ca.mas.core.store.StorageProvider.getInstance(StorageProvider.java:47)

                                                                        at com.ca.mas.core.MobileSsoFactory.reset(MobileSsoFactory.java:209)

                                                                        at com.ca.mas.foundation.MAS.stop(MAS.java:610)

                                                                        at com.ca.mas.foundation.MAS.init(MAS.java:85)

                                                                        at com.ca.mas.foundation.MAS.start(MAS.java:192)

                                                                        at XX.XXXXX.XXXXX.MApplication.onCreate(MApplication.kt:62)

                                                                        at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1192)

                                                                        at androidx.test.runner.MonitoringInstrumentation.callApplicationOnCreate(MonitoringInstrumentation.java:483)

                                                                        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6712)

                                                                        at android.app.ActivityThread.access$1300(ActivityThread.java:237)

                                                                        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)

                                                                        at android.os.Handler.dispatchMessage(Handler.java:106)

                                                                        at android.os.Looper.loop(Looper.java:223)

                                                                        at android.app.ActivityThread.main(ActivityThread.java:7656)

                                                                        at java.lang.reflect.Method.invoke(Native Method)

                                                                        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)

                                                                        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

 

Environment

Release : 2.3

Resolution

The error is harmless and can be ignored , it does not have any impact on the application 

When we call mas.start() it call mas.stop -> mas.reset -> it is failing when the start is called for the first time, and there is no config manager initialized

We will fix this in a upcoming release of the  Mobile sdk