Couldn't get config from application meta data

[niqo01]

I am seeing the following issue:

FATAL EXCEPTION: main
                  Process: com.couchsurfing.mobile.debug, PID: 9934
                  java.lang.RuntimeException: Unable to start activity ComponentInfo{com.couchsurfing.mobile.debug/com.couchsurfing.mobile.ui.WelcomeActivity}: java.lang.RuntimeException: Couldn't get config from application meta data. Was it set on your build.gradle file?
                      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2665)
                      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2726)
                      at android.app.ActivityThread.-wrap12(ActivityThread.java)
                      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1477)
                      at android.os.Handler.dispatchMessage(Handler.java:102)
                      at android.os.Looper.loop(Looper.java:154)
                      at android.app.ActivityThread.main(ActivityThread.java:6119)
                      at java.lang.reflect.Method.invoke(Native Method)
                      at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
                      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
                   Caused by: java.lang.RuntimeException: Couldn't get config from application meta data. Was it set on your build.gradle file?
                      at com.smartling.android.sdk.core.CoreImpl.a(SourceFile:46)
                      at com.smartling.android.sdk.core.CoreImpl.<init>(SourceFile:34)
                      at com.smartling.android.sdk.core.CoreImpl.getInstance(SourceFile:63)
                      at com.smartling.android.sdk.Smartling.proxy(SourceFile:56)
                      at com.couchsurfing.mobile.ui.WelcomeActivity.attachBaseContext(WelcomeActivity.java:0)
                      at android.app.Activity.attach(Activity.java:6615)
                      at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2599)
                      at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2726) 
                      at android.app.ActivityThread.-wrap12(ActivityThread.java) 
                      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1477) 
                      at android.os.Handler.dispatchMessage(Handler.java:102) 
                      at android.os.Looper.loop(Looper.java:154) 
                      at android.app.ActivityThread.main(ActivityThread.java:6119) 
                      at java.lang.reflect.Method.invoke(Native Method) 
                      at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886) 
                      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776) 

My config (2.2.3):

smartling {
  projectId = "93e7b42e8"
  auth {
    userIdentifier = "XX"
    userSecret = "XX"
  }
  mode = "context-capture"
  logLevel = "verbose"
}

[andrewforester]

Well, this exception was thrown on the line
context.getPackageManager().getApplicationInfo(context.getPackageName(), PackageManager.GET_META_DATA);
which is very strange since it means
getApplicationInfo() method threw PackageManager.NameNotFoundException.
Let's make a private Skype talk so I could learn any specific details from your project.
Skype Id: andriipanasiuk

[niqo01]

Isn't is because I did not declare a meta com.smartling.project.config in my manifest?
The documentation here: https://github.com/Smartling/android-repository does not say to add one.
Sorry I don't have skype

[andrewforester]

No, generally you don't have to do this. This configuration is exposed to manifest via Smartling plugin which you should apply in your build.gradle file. Since this exception took place in attachBaseContext method it means plugin was applied and has worked correctly. Plugin itself takes the appropriate configuration from smartling block in build.gradle file which you also have added as needed.
All to all it seems you made a correct setup. That's why I suggest there is some specific in your project which we're missing. It would be reliable and faster to discuss it in the chat.

[andrewforester]

Hi, @niqo01!
Were you able to fix that or do you still need any help?

It seems there might be an issue with the package name of your project - I'm just guessing based on our conversation. Is your project a common one built with Gradle and developing in Android Studio? Did you change the package name during the development?

[niqo01]

Hi @AndriiPanasiuk
I am sorry this last few weeks have been really busy here. Hopefully I ll be able to spare some more time soon.
I updated to 2.3.0 and still the same issue.
My project is a common one using Gradle and Android studio. We have 3 product flavors and 2 variants. Each product flavors override the applicationId.

[andrewforester]

Okay, let me try the same configuration you are using (with 3 product flavors each overriding applicationId).

[andrewforester]

I've tried a configuration with 3 product flavors and unfortunately can't reproduce your issue.
Let's try it another way.

Since the crash is caused by

context.getPackageManager().getApplicationInfo(context.getPackageName(), PackageManager.GET_META_DATA);

and the context variable is coming from attachBaseContext() method of Activity, could you insert the following code into your WelcomeActivity and start the app.

@Override
protected void attachBaseContext(Context context) {
    if (this.getBaseContext() == null) {
        super.attachBaseContext(context);
    }
    Log.d("Test", "Package name: " + context.getPackageName());
    try {
        ApplicationInfo info = context.getPackageManager().getApplicationInfo(context.getPackageName(), PackageManager.GET_META_DATA);
    } catch (PackageManager.NameNotFoundException e) {
        throw new RuntimeException(e);
    }
}

Thus, we'll see the logcat output and check if it doesn't cause an exception throwing.
Before doing that, remove please Smartling plugin applying from your build.gradle file.
Thanks!

[niqo01]

There are no crashes when removing the plugin and adding your code

Package name: com.couchsurfing.mobile.debug

The crash is not coming from context.getPackageManager().getApplicationInfo(context.getPackageName(), PackageManager.GET_META_DATA);
My guess is that var1.metaData.getString("com.smartling.project.config") return null because if you look at the generated AndroidManifest there is no com.smartling.project.config

[niqo01]

The cause is also missing when raising:

 throw new RuntimeException("Couldn\'t get config from application meta data. Was it set on your build.gradle file?");

THis exception is missing the cause.

[andrewforester]

Hi, Nicolas. @niqo01
Yes, now I see, you are right, it's because there wasn't inserted metadata as expected into your AndroidManifest.xml file which had to be inserted with Smartling plugin code. I greatly appreciate your help and will definitely rework the piece of code where that RuntimeException is throwing since it's confusing a bit.
I created custom build of our plugin with additional logging to identify the issue and to understand why that metadata isn't exposed into your manifest.
To use it please do the following:

• in the buildscript section of your app's build.gradle use changed repo and version name for the plugin dependency

buildscript {
    ...
    repositories {
        ...
        maven { url "https://raw.githubusercontent.com/Smartling/android-repository/snapshots" }
    }
    dependencies {
       ...
       classpath "com.smartling.android:plugin:2.3.0-COUCHSURFING-SNAPSHOT"
    }
}

• execute ./gradlew app:clean app:assemble{flavor_name}Debug command
• give me the log outputs started with Smartling: string

Thank you a lot!

[niqo01]

I replaced user id and secret with XX

Smartling: Config for playUiTest: SmartlingConfig{name='playUiTest', logLevel='verbose', mode='context-capture', otaServing=null, auth=Auth{userIdentifier='XX', userSecret='XX'}}
Smartling: Add process manifest action to playUiTest
Smartling: Config for playDebug: SmartlingConfig{name='playDebug', logLevel='verbose', mode='context-capture', otaServing=null, auth=Auth{userIdentifier='XX', userSecret='XX'}}
Smartling: Add process manifest action to playDebug
Smartling: Config for playRelease: SmartlingConfig{name='playRelease', logLevel='verbose', mode='context-capture', otaServing=null, auth=Auth{userIdentifier='XX', userSecret='XX'}}
Smartling: Add process manifest action to playRelease
Smartling: Config for playDevUiTest: SmartlingConfig{name='playDevUiTest', logLevel='verbose', mode='context-capture', otaServing=null, auth=Auth{userIdentifier='XX', userSecret='XX'}}
Smartling: Add process manifest action to playDevUiTest
Smartling: Config for playDevDebug: SmartlingConfig{name='playDevDebug', logLevel='verbose', mode='context-capture', otaServing=null, auth=Auth{userIdentifier='XX', userSecret='XX'}}
Smartling: Add process manifest action to playDevDebug
Smartling: Config for playDevRelease: SmartlingConfig{name='playDevRelease', logLevel='verbose', mode='context-capture', otaServing=null, auth=Auth{userIdentifier='XX', userSecret='XX'}}
Smartling: Add process manifest action to playDevRelease

Later

Smartling: Start Transforming Manifest at /home/niqo/workspace/couchsurfing/couchsurfing-android/app/build/intermediates/manifests/full/playDev/debug/AndroidManifest.xml
Smartling: Manifest parsed
Smartling: Metadata created and parsed
Smartling: Metadata node has been added to original manifest
Smartling: Modified manifest has been written to its file

[dmapr]

I have run into this issue as well. What's really strange is that in my case

• The meta-data tag is generated and does appear in the manifest as expected
• The crash because the metadata is missing only happens in the debug variant, not in the release
• Commenting out the Smartling plugin and placing the generated value in the manifest manually works in the debug mode as well

The only thing that I have noticed that is different in the generated manifest file is that in the debug version we use Leak Canary and the following items are generated in the manifest preceding the Smartling meta-data tag:
`

    <activity android:enabled="false" android:icon="@drawable/leak_canary_icon" android:label="@string/leak_canary_display_activity_label" android:name="com.squareup.leakcanary.internal.DisplayLeakActivity" android:taskAffinity="com.squareup.leakcanary" android:theme="@style/leak_canary_LeakCanary.Base">
        <intent-filter>
            <action android:name="android.intent.action.MAIN"/>

            <category android:name="android.intent.category.LAUNCHER"/>
        </intent-filter>
    </activity>
    <activity android:enabled="false" android:icon="@drawable/leak_canary_icon" android:label="@string/leak_canary_storage_permission_activity_label" android:name="com.squareup.leakcanary.internal.RequestStoragePermissionActivity" android:taskAffinity="com.squareup.leakcanary" android:theme="@style/leak_canary_Theme.Transparent"/>

`
I printed out the entire metadata in the Application.onCreate() and all metadata except for the smartling one is there if I let the plugin generate it. If I add it manually, then all metadata including the smartling one is accessible in code. Ditto in the release variant where the leak canary stuff isn't addedd.

[andrewforester]

Hey @dmapr! Sorry for late response.
So, for which build variant Smartling plugin does generate metadata in your case and for which doesn't?

[dmapr]

Hi @AndriiPanasiuk,

sorry I wasn't quite clear. The metadata gets generated in ALL cases, what is different is that in the debug version the app can't read it.

[andrewforester]

@dmapr thanks, working on that.
Could you then send me the final generated manifest for debug variant (from intermediates/manifests/full folder)? Possibly with obfuscated code you don't want to expose but still retaining its structure.
apanasiuk@smartling.com
Thank you!