Databases
StackOverflow2013
Postsdbo
POLocalizations for abc_* strings (from com.android.support:appcompat-v7) appeared in my APK
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POLocalizations for abc_* strings (from com.android.support:appcompat-v7) appeared in my APK
    primarykey
    data
    text
    <p>In recent builds of an android application I wrote I see the appearance of a lot of file containing translations for several strings that I never added.</p> <pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;resources&gt; &lt;string name="abc_action_bar_home_description"&gt;Navigate home&lt;/string&gt; &lt;string name="abc_action_bar_up_description"&gt;Navigate up&lt;/string&gt; &lt;string name="abc_action_menu_overflow_description"&gt;More options&lt;/string&gt; &lt;string name="abc_action_mode_done"&gt;Finished&lt;/string&gt; &lt;string name="abc_activity_chooser_view_see_all"&gt;See all&lt;/string&gt; &lt;string name="abc_activitychooserview_choose_application"&gt;Choose an app&lt;/string&gt; &lt;string name="abc_searchview_description_clear"&gt;Clear query&lt;/string&gt; &lt;string name="abc_searchview_description_query"&gt;Search query&lt;/string&gt; &lt;string name="abc_searchview_description_search"&gt;Search&lt;/string&gt; &lt;string name="abc_searchview_description_submit"&gt;Submit query&lt;/string&gt; &lt;string name="abc_searchview_description_voice"&gt;Voice search&lt;/string&gt; &lt;string name="abc_shareactionprovider_share_with"&gt;Share with&lt;/string&gt; &lt;string name="abc_shareactionprovider_share_with_application"&gt;Share with %s&lt;/string&gt; &lt;/resources&gt; </code></pre> <p>Those strings seems to come from the <a href="http://developer.android.com/reference/android/support/v7/mediarouter/R.string.html" rel="nofollow"><code>android.support.v7.mediarouter.R.string</code></a> file and that is coherent with the fact that I am using the compatibility support library (But I am not using mediarouter)</p> <p>I compiled my application with gradle and using Android Studio and in both case (Unsurprisingly since they are both using the same scripts).</p> <p>How can I get rid of them? That is particularly important because my app is now listed in the Play Store as supporting 56 languages when it actually supports only 2.</p> <p>I see that it first happened when I first switched from API level 8+ to API level 7+, but now even if I choose an higher API level I still have them.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmariosangiorgio
    1. USmariosangiorgio
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CODid test what happens if you switch your device to a language that is not supported by your app? (I suspect the app can crash.)
      singulars
      1. POLocalizations for abc_* strings (from com.android.support:appcompat-v7) appeared in my APK
      1. US18446744073709551615
    2. COLuckily (I tested it on an emulator) it does fall back to the default language. Still it is very annoying
      singulars
      1. POLocalizations for abc_* strings (from com.android.support:appcompat-v7) appeared in my APK
      1. USmariosangiorgio
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload