Bug 40184 - Application properties do not persist in mode with linker enabled
Summary: Application properties do not persist in mode with linker enabled
Status: RESOLVED DUPLICATE of bug 36710
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 2.1.0
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jason Smith [MSFT]
Depends on:
Reported: 2016-04-07 03:04 UTC by Cody Beyer (MSFT)
Modified: 2016-12-06 16:46 UTC (History)
7 users (show)

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

Sample (90.36 KB, application/zip)
2016-04-07 03:05 UTC, Cody Beyer (MSFT)

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 Cody Beyer (MSFT) 2016-04-07 03:04:54 UTC
# Description

The following sample app demonstrates an issue with application properties, where  a value will persist in “Debug” but not in “Release”

Initial theory was that it had to do with Android permissions, however setting permissive values does not resolve the issue.

Further testing revealed that the issue only occurs when the linker is enabled. if the linker is off, properties persist

#  Sample


# Video


# Steps to Reproduce

1. Download sample
2. Enable Linker set to Link SDK Assemblies
3. Deploy to Android emulator
4. Type something into entry field
5. Toolbar > Save
6. Exit app
7. Open app

# Expected Results

Value should persist

# Actual Results

Value is no longer present

# Versions

=== Xamarin Studio ===

Version 6.0 (build 4801)
Installation UUID: 7d0f2655-6450-4e53-8bc6-ad3aac410706
	Mono 4.4.0 (mono-4.4.0-branch/f8474c4) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 404000040

=== Xamarin.Profiler ===

Version: 0.32.0
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Apple Developer Tools ===

Xcode 7.3 (10183.3)
Build 7D175

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: 5f11db8
Branch: master
Build date: 2016-03-25 21:26:55-0400

=== Xamarin.Android ===

Version: (Business Edition)
Android SDK: /Users/codybeyer/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		4.0.3 (API level 15)
		4.4   (API level 19)
		5.1   (API level 22)
		6.0   (API level 23)

SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.1
SDK Build Tools Version: 23.0.1

Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

Android Designer EPL code available here:

=== Xamarin Android Player ===

Version: 0.6.5
Location: /Applications/Xamarin Android Player.app

=== Xamarin.Mac ===

Version: (Business Edition)

=== Xamarin Inspector ===

Hash: 2a5f6e9
Branch: master
Build date: Thu Mar 31 18:37:26 UTC 2016

=== Build Information ===

Release ID: 600004801
Git revision: f73f730c738baf8701a5892b7af64fd468d1dc0c
Build date: 2016-03-14 14:28:06-04
Xamarin addins: 3af7be6c701eb0137645a03e38b82f23b65738c3
Build lane: monodevelop-lion-cycle7

=== Operating System ===

Mac OS X 10.11.4
Darwin clbmacbook.local 15.4.0 Darwin Kernel Version 15.4.0
	Fri Feb 26 22:08:05 PST 2016
	root:xnu-3248.40.184~3/RELEASE_X86_64 x86_64

=== Enabled user installed addins ===

Xamarin Inspector
Comment 1 Cody Beyer (MSFT) 2016-04-07 03:05:47 UTC
Created attachment 15636 [details]
Comment 2 Samantha Houts [MSFT] 2016-09-13 16:16:46 UTC
This does not appear to be a Forms bug; it is caused by the System.Runtime.Serialization.dll being stripped out by the linker. This should be resolved by the fix to Bug 36710, which has yet to be released.

In the meantime, please workaround the issue by adding System.Runtime.Serialization to the list of ignored assemblies in the Android project properties (Android Options >> Linker >> Skip linking assemblies). We have verified that this works.

Warm regards,
Xamarin Forms Team

*** This bug has been marked as a duplicate of bug 36710 ***
Comment 3 Ejoe 2016-12-06 16:46:44 UTC
Hi guys,

this workaround doesn't fix the issue for me...
I'm building with the linker behaviour : Link SDK assemblies only.

Should I change it?