Skip to content
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

Visual Studio 4 Mac 8.10.18 (current running on VM macOS 11) is broken running Xamarin.iOS app with touch gestures. Need upgrade #5120

Closed
1 of 7 tasks
haavamoa opened this issue Feb 22, 2022 · 8 comments
Assignees

Comments

@haavamoa
Copy link

Description

Hi, the past days we have experienced issues with our Xamarin.iOS app version where touch gestures are not working in our app. This was resolved in Visual Studio 4 Mac 8.10.19. The problem is that our VMs that build the app is running macOS11 which has 8.10.18, so we are unable to deliver our app with this critical error.

I can't seem to find any issue regarding this anywhere, but we do see that the new version are handling DisposableObjects differently from Xamarin.iOS:
https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2019-mac-relnotes#--visual-studio-2019-for-mac-version-81019-810192

Virtual environments affected

  • Ubuntu 18.04
  • Ubuntu 20.04
  • macOS 10.15
  • macOS 11
  • Windows Server 2016
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

20220212.1

Is it regression?

No response

Expected behavior

Touch gestures working in iOS app.

Actual behavior

Touch gestures does not work in iOS app.

Repro steps

  1. Create a Xamarin.Forms app, a view element with a gesture recogniser that changes something in the page.
  2. Run the app locally with Visual Studio 4 Mac latest version, observe that it works.
  3. Run the app through azure pipeline running Visual Studio 4 Mac 8.10.18 and download the app, observe that it does not work.
@haavamoa
Copy link
Author

haavamoa commented Feb 22, 2022

I can see that you have released pre-releases of new macOS11 that runs 8.10.19, but I am unable to understand how I can use that in my azure DevOps pipeline. If you could please provide me some links on how to do that, it would be appreciated so we can deliver our iOS app running our pipeline.

@nikolai-frolov nikolai-frolov added awaiting-deployment Code complete; awaiting deployment and/or deployment in progress and removed needs triage labels Feb 22, 2022
@nikolai-frolov
Copy link
Contributor

Hello, you are correct, new macOS-11 image with 8.10.19.2 Visual Studio for Mac will be deployed during this week to all environments. After that you will be able to use it as usual.

@nikolai-frolov nikolai-frolov self-assigned this Feb 22, 2022
@miketimofeev
Copy link
Contributor

@haavamoa VS4mac has been updated.
I'm going to close the issue. Feel free to contact us if you have any concerns.
Thank you!

@miketimofeev miketimofeev removed the awaiting-deployment Code complete; awaiting deployment and/or deployment in progress label Feb 25, 2022
@haavamoa
Copy link
Author

haavamoa commented Mar 1, 2022

Seems like the bug still persists after update.

From initialize step in pipeline:
image

When building locally with the same build configuration, it works. Here's VS 4 Mac version on my machine:
image

When comparing Xamarin.iOS versions I see that pipeline is using 15.4 and I am running 15.6, trying to select that specific version to see if that helps.

@haavamoa
Copy link
Author

haavamoa commented Mar 1, 2022

No difference if I selected 15.6 of Xamarin.iOS. Help!

@miketimofeev miketimofeev reopened this Mar 1, 2022
@haavamoa
Copy link
Author

haavamoa commented Mar 1, 2022

I actually found out that this was a problem with the third party XamarinCommunityToolkit dependency we have. I somehow have to enable both mtouch argument --interpreter + the Visual Studio 4 Mac checkbox for enabling Mono Interpreter for a touch gesture effect to work:
xamarin/XamarinCommunityToolkit#1823

This was not turned on in our release configuration for the iOS app. So this was a bit confusing to know what was wrong I'm afraid.

@miketimofeev
Copy link
Contributor

@haavamoa thanks for the update! Do you still need any help from our side or we can close the issue?

@haavamoa
Copy link
Author

haavamoa commented Mar 1, 2022

i’ll close it. 👍

@haavamoa haavamoa closed this as completed Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants