Bug 57816 - Xamarin.GooglePlayServices.Maps builds with "packaged_resources does not exist" error.
Summary: Xamarin.GooglePlayServices.Maps builds with "packaged_resources does not exis...
Status: CONFIRMED
Alias: None
Product: Android
Classification: Xamarin
Component: General (show other bugs)
Version: 7.3 (15.2)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2017-06-27 22:49 UTC by Mark McLemore
Modified: 2017-06-27 23:10 UTC (History)
1 user (show)

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


Attachments
Test project (2.81 MB, application/zip)
2017-06-27 22:49 UTC, Mark McLemore
Details
System info (3.18 KB, text/plain)
2017-06-27 22:50 UTC, Mark McLemore
Details

Description Mark McLemore 2017-06-27 22:49:31 UTC
Created attachment 23154 [details]
Test project

Building a new app after adding the Xamarin.GooglePlayServices.Maps 10.2.1 NuGet causes the following error:

The file "obj\Debug\android\bin\packaged_resources" does not exist.

It's easy to repro:

1. Create a blank Xamarin.Android app.
2. Use the NuGet Manager to add Xamarin.GooglePlayServices.Maps 10.2.1 to the project.
3. Build.

Manually deleting bin/obj and rebuilding does not clear up this error. Sample project and system info attached.
Comment 1 Mark McLemore 2017-06-27 22:50:11 UTC
Created attachment 23155 [details]
System info
Comment 2 Mark McLemore 2017-06-27 22:57:04 UTC
The following sample app successfully built with previous versions of Xamarin.GooglePlayServices.Base (42.1001.0):

https://developer.xamarin.com/samples/monodroid/Firebase/FCMNotifications

Building this sample against Xamarin.GooglePlayServices.Base 42.1021.1 results in the same "packaged resources does not exist" build error.
Comment 3 Mark McLemore 2017-06-27 23:06:30 UTC
Seeing the same problem with Xamarin.GooglePlayServices.Base 42.1024.0-beta1 and Xamarin.GooglePlayServices.Base 42.1001.0, so it looks like the problem is not in the play services bindings but perhaps elsewhere.
Comment 4 Mark McLemore 2017-06-27 23:10:47 UTC
Manually creating an empty obj\Debug\android\bin\packaged_resources file seems to workaround the problem: it builds, but with warnings.

Note You need to log in before you can comment on or make changes to this bug.