Bug 32522 - Google Play touchscreenBlocksFocus No resource identifier
Summary: Google Play touchscreenBlocksFocus No resource identifier
Alias: None
Product: Components
Classification: Xamarin
Component: Xamarin Components ()
Version: Production (addons.xamarin.com)
Hardware: PC All
: --- normal
Target Milestone: ---
Assignee: Jon Dick
Depends on:
Reported: 2015-07-28 10:01 UTC by Stuart
Modified: 2015-07-31 10:53 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Stuart 2015-07-28 10:01:39 UTC
Error APT0000: No resource identifier found for attribute 'touchscreenBlocksFocus' in package 'android' (APT0000) (Test)

Can't compile unless API target is set to level 21

Common problem. See https://forums.xamarin.com/discussion/comment/141636
Comment 1 Atsushi Eno 2015-07-28 12:02:33 UTC
I believe you should use Google Play Services (Froyo) package that builds as old as Froyo. The latest Xamarin.Android does not suppport pre-Gingerbread anymore though.

Also you could specify different minSdkVersion (whatever you need) from targetSdkVersion (specify 21 or higher).

I'm leaving this report to the Component team (who actually creates those packages) for their comments.
Comment 2 Jon Dick 2015-07-31 10:53:40 UTC
The fix is in the forum post, set your target api level to 21 or higher.

Unfortunately, this is the same on Google's own tooling for these libraries since aapt needs to compile against the higher api level to see the attributes.  You can still set your minSdkVersion as Atsushi mentioned to a lower API level.