Azure-devops-docs: More detail

[indyjason79]

You do not cover signing or any of the other tasks involved. I would strongly suggest covering every step/task needed, especially signing the APK since that's what I've been stuck on the most trying to set this up for our company. You should also cover setting up pre-reqs such as installing Android SDK Levels and setting the ANDROID_HOME environment. I've been working on this for 2 days and still can't produce an APK that works.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: c45a95ce-73c8-861e-f92d-a26f1667aa60
• Version Independent ID: ecb82128-cdf4-3834-62c1-2cf61989ab5e
• Content: Build your Xamarin app
• Content Source: docs/pipelines/apps/mobile/xamarin.md
• Product: devops
• GitHub Login: @andyjlewis
• Microsoft Alias: alewis

[davidstaheli]

Thanks for creating this issue, Jason. I'd like us to document what you suggested ASAP. I'm sorry for the wasted time and frustration you went through. If you haven't exhausted all of your available time, could you please email me at [email protected]? We can help you get things working and then use our weak spots to improve the product and guide what we put in the documentation, including what you suggested above.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[davidstaheli]

Keep-alive

[indyjason79]

Sorry, I had forgot to reply to this. I'll email you this week to help with
the documentation.

Thanks,
Jason Willett

On Sun, Mar 10, 2019, 2:43 PM David Staheli [e-mail]
wrote:

Keep-alive

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/vsts-docs/issues/1656#issuecomment-471332268,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEz4PZ4Ym9xXvT-1wUSta5Bya1YtVbljks5vVVJpgaJpZM4WbtIo
.

[cxwtool]

This issue hasn't been updated in more than 180 days, so we've closed it. If you feel the issue is still relevant and needs fixed, please reopen it and we'll take another look. We appreciate your feedback and apologize for any inconvenience.