card.io strings do not change with proguard

Question

I have a problem with obfuscation on card.io.

I'm changing the strings on strings.xml with the tags given on card.io official page and while I'm debugging, the app uses the changed strings. But when i export signed apk with proguard, the app uses its own strings. Could you help me? What am I missing?

This is my proguard.cfg content: (I use the sample app's proguard file.)

-optimizationpasses 5
-dontusemixedcaseclassnames
-dontskipnonpubliclibraryclasses
-dontpreverify
-verbose
-optimizations !code/simplification/arithmetic,!field/*,!class/merging/*

-keep public class * extends android.app.Activity
-keep public class * extends android.app.Application
-keep public class * extends android.app.Service
-keep public class * extends android.content.BroadcastReceiver
-keep public class * extends android.content.ContentProvider
-keep public class * extends android.app.backup.BackupAgentHelper
-keep public class * extends android.preference.Preference

-keepclasseswithmembernames class * {
    native <methods>;
}

-keepclasseswithmembers class * {
    public <init>(android.content.Context, android.util.AttributeSet);
}

-keepclasseswithmembers class * {
    public <init>(android.content.Context, android.util.AttributeSet, int);
}

-keepclassmembers class * extends android.app.Activity {
   public void *(android.view.View);
}

-keepclassmembers enum * {
    public static **[] values();
    public static ** valueOf(java.lang.String);
}

-keep class * implements android.os.Parcelable {
  public static final android.os.Parcelable$Creator *;
}

-keep class io.card.** 
-keepclassmembers class io.card.** {
   *;
}

## Good practice so that you don't end up logging sensitive info.
# Remove debug, verbose, and info Log calls
-assumenosideeffects class android.util.Log {
    public static *** d(...);
    public static *** v(...);
    public static *** i(...);
    ## Uncomment to remove warnings and errors as well
    # public static *** w(...);
    # public static *** e(...);
}

score 3 · Accepted Answer · answered Sep 11 '13 at 18:04

3

Jeff from card.io here.

card.io no longer supports the strings.xml file as of version 3.1.0+, because the SDK provides translations. Are you using the latest version?

If not, please download the latest SDK. You can either rely on the device language settings to automatically bring up the correct localizations, or force a locale with CardIOActivity.EXTRA_LANGUAGE_OR_LOCALE (see javadocs).

answered Sep 11 '13 at 18:04

Jeff Brateman

3,229
2
20
26

Hi Jeff, I was using **3.0.6**, downloaded **3.1.1**. I set to tr - scanIntent.putExtra(CardIOActivity.EXTRA_LANGUAGE_OR_LOCALE, "tr")- Thanks it changed to tr, **but** app uses your localization strings. I could't changed with mines. I use as "values-tr". Should I add anything else ? – quick release Sep 12 '13 at 07:04
Nope. Those values-* files are now obsolete. Please let us know if a translation needs fixing! – Jeff Brateman Sep 16 '13 at 17:18
If I could change with my customized strings, it would be better. But as long as it gives the suitable results with the setted localization, it is enough. Thanks. – quick release Sep 17 '13 at 14:18

score 0 · Answer 2 · answered Sep 12 '13 at 14:59

0

To add to Jeff's response, if there's a problem with a translation, we'd like to fix it! Please file bugs here.

I've also updated the example app to remove the strings examples. Thanks for letting us know that it was out of date.

answered Sep 12 '13 at 14:59

tomwhipple

2,850
27
28

card.io strings do not change with proguard

2 Answers2