This error indicates that an incorrect setting was applied in the MceConfig file. It might be an issue with an incorrect baseUrl or an incorrect senderID set in the MceConfig.json file.

When you run an Android app for the first time after installation or upgrade, the user sees the following entries in the debug log:

   RegistrationManager: Error while registering the sdk

RegistrationManager: java.io.FileNotFoundException: https://mobile-api-lib-us-0.brilliantcollector.com/3.0/regist...gcm/gcrnPqYCgR

RegistrationManager:     at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:238)

RegistrationManager:     at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210)
    

 https://mobile-api-lib-us-0.brilliantcollector.com

To resolve this issue, the developer must verify these configurations:

1. Incorrect baseUrl set in the MceConfig.json file.

   The baseUrl refers to the user's Acoustic Campaign environment. Acoustic geographically separates environments to cater for local privacy laws and to provide greater scalability. See Setting the baseURL to get the correct setting for the baseUrl.

2. Incorrect senderID set in the MceConfig.json file.

   The app-key is generated in Acoustic Campaign and is needed by the SDK to know which mobile database to create the contacts. If the user enters an appkey that does not exist, then the contact creation fails.