-
Notifications
You must be signed in to change notification settings - Fork 534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Xamarin.Android.Build.Tasks] Always create the debug.keystore #1148
Conversation
This PR confuses me. The original bug is that the Additionally, the shared runtime creation logic within Using I would prefer that the |
<Target Name="_ResolveAndroidSigningKey" DependsOnTargets="$(_OnResolveMonoAndroidSdks)"> | ||
<Target Name="_CreateAndroidDebugSigningKey" | ||
Condition="!Exists ('$(_ApkDebugKeyStore)')" | ||
DependsOnTargets="$(_OnResolveMonoAndroidSdks)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this DependsOnTargets
required? The only caller -- _ResolveAndroidSigningKey
-- has $(_OnResolveMonoAndroidSdks)
within its DependsOnTargets
anyway.
Fixes https://bugzilla.xamarin.com/show_bug.cgi?id=61065 If a user sets the `$(AndroidKeyStore)` to `True` for a debug configuration they will get the following error. [MESSAGE] jarsigner error: java.lang.RuntimeException: keystore load: /Users/$(user)/.local/share/Xamarin/Mono for Android/debug.keystore (No such file or directory) Note this will only happen if they have NEVER build with `$(AndroidKeyStore)` set to `False`. This is because we don't always generate the `debug.keystore`. So rather than hitting this issue we should always generate the `debug.keystore` regardless of what the setting for `$(AndroidKeyStore)` is. This commit splits out the keystore generation into its own target. This target will check the existance of the file and generate it if required. We also move all the debug key property values into Properties so that they can be updated in one place.
@jonpryor I removed the properties.. One thing to note.. our assumption that |
Hi, interestingly it also fails if i refer to another keystore file. VS still looking for debug.keystore. please see the forum post more information. |
Fixes: xamarin/monodroid#1147 Fixes: xamarin/monodroid#1150 Fixes: xamarin/monodroid#1123 Changes: xamarin/monodroid@3586135...06e80c5 * xamarin/monodroid@06e80c567: [tools/msbuild] FastDeploy is not ignoring warnings in output (dotnet#1151) (dotnet#1152) * xamarin/monodroid@1f08686de: [tools/msbuild] <FastDeploy/> Length cannot be less than zero (dotnet#1148)
Fixes: xamarin/monodroid#1123 Fixes: xamarin/monodroid#1147 Fixes: xamarin/monodroid#1150 Changes: xamarin/monodroid@3586135...06e80c5 * xamarin/monodroid@06e80c567: [tools/msbuild] FastDeploy is not ignoring warnings in output (#1151) (#1152) * xamarin/monodroid@1f08686de: [tools/msbuild] <FastDeploy/> Length cannot be less than zero (#1148)
Fixes: xamarin/monodroid#1147 Changes: http://github.com/xamarin/monodroid/compare/27736a7ffc48d606ab45598f761e873f8572f46a...daa2fb6ca52ecfd0884177da5b57501bb4dda3c6 * xamarin/monodroid@daa2fb6ca: Bump to xamarin/xamarin-analysis@9524531 (#1149) * xamarin/monodroid@bca44d592: [tools/msbuild] <FastDeploy/> Length cannot be less than zero (#1148) * xamarin/monodroid@2df384fe2: [tools/msbuild] improve XA0010 error message (#1144) * xamarin/monodroid@b2da84d5f: [tools/msbuild] remove MSBuild targets related to the Xamarin Inspector (#1143)
Fixes https://bugzilla.xamarin.com/show_bug.cgi?id=61065
If a user sets the
$(AndroidKeyStore)
toTrue
for adebug configuration they will get the following error.
Note this will only happen if they have NEVER build with
$(AndroidKeyStore)
set toFalse
. This is because wedon't always generate the
debug.keystore
.So rather than hitting this issue we should always generate the
debug.keystore
regardless of what the setting for$(AndroidKeyStore)
is. This commit splits out the keystore generation into its own
target. This target will check the existance of the file and
generate it if required. We also move all the debug key property
values into Properties so that they can be updated in one place.