I just bumped up the build target on one of my apps to Android 2.0, exported a signed APK, and it installed and ran OK from the Browser app on the Android 1.5 emulator.
So I guess the problem doesn't always occur. I wonder what we are doing different. What are you using for the uses-sdk element in your manifest? My test used: <uses-sdk android:minSdkVersion="3" android:targetSdkVersion="4" /> Although I think the wrong values there would result in a "cannot be installed on this phone" error rather than a parse error. On Nov 15, 12:55 pm, Max Binshtok <max.binsh...@gmail.com> wrote: > I did signed export of the package while setting the target as 2.0. > Then I tried to install the package by downloading it *through > browser* (OTA download) on all the emulators. On 1.5, when I click on > the download in order to install the package, I get the > > "Parse Error: There is a problem parsing the package" > > It works on 1.6 and 2.0 though. > > Compiling with 1.6 set as the target seems to install on all the > emulators ok. > > Is it zipalign issue? Or if not - can someone clarify that to me? For > now I don't use any 2.0 APIs, so I can just use 1.6 but in future - > who knows and if this is going to be still a problem, how should be go > about backward compatibility? > > Regards, > Max. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
