Android document says several advantages of android:targetSdkVersion. But, I faced following issue.
Here is my case.
android:minSdkVersion="10"
android:targetSdkVersion="15"
...
<activity ...
android:configChanges="orientation|keyboardHidden"
...
Since v3.2 ScreenSize is additionally required at configChanges to handle orientation change.
But, in this case, minSdkVersion is "10" so, ScreenSize cannot be used.
The problem is that targetSdkVersion is "15".
So, framework doesn't call onConfigurationChanged() callback when orientation is changed.
This is unavoidable and unexpected.
Eventually, I gave up using 'targetSdkVersion'.
I'm not sure there are any other workarounds for these cases, but after experiencing above case, I am trying to Not-To-Use targetSdkVersion option...
'Domain > Android' 카테고리의 다른 글
[Android] SurfaceView + SlidingDrawer issue (0) | 2012.10.17 |
---|---|
[Android] Using SQLite cursor of quite-big-database asynchronously. (0) | 2012.10.10 |
Policy of Google Play to consider registering App to Android Google Play. (0) | 2012.10.04 |
Points to consider for recycling Bitmap of ImageView. (0) | 2012.09.21 |
[Android] Developing Android-native-library on 64bit build machine (0) | 2011.09.15 |