Not the expected Target sdk version?


#1

Exploring new (to me) apps… But what is this?


#2

Seeing this too, strange, albeit it’s an app build in 2012 for Android 1.5.

Any other apps doing this?

aapt dump badging org.beide.bomber_1.apk

application-label:'Bomber'
application-icon-160:'res/drawable/icon.png'
application: label='Bomber' icon='res/drawable/icon.png'
launchable-activity: name='org.beide.bomber.BomberActivity'  label='Bomber' icon='res/drawable/icon.png'
uses-permission: name='android.permission.WRITE_EXTERNAL_STORAGE'
uses-implied-permission: name='android.permission.WRITE_EXTERNAL_STORAGE' reason='targetSdkVersion < 4'
uses-permission: name='android.permission.READ_PHONE_STATE'
uses-implied-permission: name='android.permission.READ_PHONE_STATE' reason='targetSdkVersion < 4'
uses-permission: name='android.permission.READ_EXTERNAL_STORAGE'
uses-implied-permission: name='android.permission.READ_EXTERNAL_STORAGE' reason='requested WRITE_EXTERNAL_STORAGE'
feature-group: label=''
  uses-feature: name='android.hardware.faketouch'
  uses-implied-feature: name='android.hardware.faketouch' reason='default feature for all apps'
main
other-activities
supports-screens: 'normal'
supports-any-density: 'false'
locales: '--_--'
densities: '160'

Maybe it’s the density 160 thing?


#3

By exploring I mean I’m going through apps alphabetically and downloading ones that interest me. The meaning of “densities” is lost on me. Lol. I’m a mere user.


#4

Seems like a bug in the logic for when the targetSdkVersion is not set in the APK. It should default to 1 then.