Xamarin iOS gesture recognizers do not work in 17.0.1 #14956
Comments
Can't reproduce both on the Simulator as well as on a physical device. Please ping me when you find this and can add a reproduction project for us to try. |
I don't know of a project you can try, but I am still having this issue. It does not happen when using the simulator, only when loading directly to a phone. In Android the gesture recognizer works, but in iOS it does not work. This has not been fixed. |
@lukies97 thanks for finding this issue here! I'll reopen it for now, but I can't reproduce it myself. As mentioned: I did try on a phone :) So I would really need a reproduction case first to see what is wrong in which scenario. |
@jfversluis I was able to reproduce in 2022 Community using the WorkingWithGestures Sample Project on a USB connected iPhone XS. |
@melmulcahy32 thanks! Not sure what to tell you... For me that just works... 😩 |
😭 perhaps it's an environment thing. I know my dev team uses MacStadium and builds apps using a virtual Mac. |
I was the user who reported this. I think it may be worth mentioning that I followed some other steps from a Microsoft rep to fix a provisioning problem in VS2019. This was to install VS 2022, then copy the iSign.Core.dll, iSign.Core.pdb and System.Formats.Asn1.dll files from /tools/msbuild/ios to C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\iOS. |
@grvingit but you are still seeing this behavior? |
I have the same issue, with provided WorkingWithGestures sample and my own codes. Android no issues on same apps. . USB direct with hot reload, no MAC pairing, studio 2019 and 2022. |
I also followed the same steps as @grvingit and I am still having trouble with the gesture recognizer. I didn't have the issues in 2019 until after followed those steps and now I have the issue in VS2019 and VS2022. |
@jfversluis Yes, I am still seeing it. I had to remove all gesture recognizers in my app and replace them with image buttons in order to get an urgent update out, but this evening when I tried them again they still do not work. |
@MiekVenter did you also do something with the copying of DLLs as mentioned above? |
No, no copying. New clean 2022 installation, first project ever compiled on new installation was the demo. |
You're running this from Windows through Hot Restart (directly on a physical iOS device)? Or do you have it paired to a Mac? |
Direct on hot restart |
I will have an MAC box by next week. |
@chamons @dalexsoto I see this happened before in #10162 any chance this has regressed? |
For me the problem only occurs with Hot Restart. I've just tried it through a paired Mac and gesture recognizers works fine. Unfortunately for me developing and debugging this way is not an option as deploying is too slow - it takes a number of minutes each time. |
Yeah the cause seems to be Hot Restart here, found an earlier issue that describes the same, maybe there is a regression there. We just need to wait for them to wake up ;) |
Did they ever wake up? ;) 10 Days is a long sleep. |
They work very hard! No news yet unfortunately :( |
I appreciate that they work hard. I was just trying at some levity. Hopefully they can figure out something soon. |
This comment was marked as off-topic.
This comment was marked as off-topic.
I've raised it again to the people responsible, thanks for your patience! |
I think VS 2022 Preview 5 has a lot of patches regard this issue. It's been promising for my team so far. |
Me and a colleague are now experiencing this on Mac with VS 4 Mac 8.10.17 and 8.10.18. Running M1 MacBooks. |
I am experiencing this exact problem after upgrading VS Enterprise from 17.0.0 to 17.0.6. GestureRecognizers not working on USB connected iPhone deployed using Hot Reload. Everyting is working fine on Android. The problem is reproduceable using the Tabbed New Mobile App Template. Dump of installed products (from the About-menu): Installed Version: Enterprise Visual C++ 2022 00476-80000-00000-AA059 ASP.NET and Web Tools 2019 17.0.796.18217 Azure App Service Tools v3.0.0 17.0.796.18217 C# Tools 4.0.1-1.21568.1+6ab6601178d9fba8c680b56934cd1742e0816bff Common Azure Tools 1.10 Extensibility Message Bus 1.2.6 (master@34d6af2) Microsoft JVM Debugger 1.0 Microsoft MI-Based Debugger 1.0 Microsoft Visual C++ Wizards 1.0 Microsoft Visual Studio VC Package 1.0 Mono Debugging for Visual Studio 17.0.11 (54f19d2) NuGet Package Manager 6.0.1 ProjectServicesPackage Extension 1.0 TypeScript Tools 17.0.1001.2002 Visual Basic Tools 4.0.1-1.21568.1+6ab6601178d9fba8c680b56934cd1742e0816bff Visual F# Tools 17.0.0-beta.21522.2+6d626ff0752a77d339f609b4d361787dc9ca93a5 Visual Studio Code Debug Adapter Host Package 1.0 Visual Studio IntelliCode 2.2 VisualStudio.DeviceLog 1.0 VisualStudio.Foo 1.0 VisualStudio.Mac 1.0 Xamarin 17.0.0.343 (d17-0@fb07a17) Xamarin Designer 17.0.0.183 (remotes/origin/d17-0@a351f0f1f) Xamarin Templates 17.0.17 (9e779b0) Xamarin.Android SDK 12.1.0.5 (d17-0/6b0e6b2) Xamarin.iOS and Xamarin.Mac SDK 15.4.0.0 (8fc41ae82) |
We are now experiencing this in our production app by using Azure Devops pipeline, because pipeline is using Visual Studio 4 Mac 8.10.18 with the macOS11 virtual environment. Locally on my machine I am running 8.10.19 and it works as expected. So if you are experiencing this issue, check your Mac's VS4Mac version. |
Is there some progress on the issue? We've been affected for almost three months now. Working on UI controls is hardly possible. |
This comment was marked as off-topic.
This comment was marked as off-topic.
@nemekzg could you please post details about version numbers of tools that you are using? Are you using Hot Restart? |
I'm the user that reported this. It happens in VS 2019 and VS 2022. It started around the time 2022 came out. It occurs using Hot Restart, but not when the iPhone is connected via a Mac (I'm developing in Windows). |
@jfversluis: the dump of my current configuration is pasted below. For the last couple of months, I've tried both VS 2019 and VS 2022 (the latter also in the preview version) but the problem is still there. We use Xamarin Forms 5.0.0.2337 and we do use HotRestart. Our setup consists of a Windows machine that deploys the project to an iPhone via USB. We also use a Macincloud instance. The problem seems to disappear at times with no apparent reason and then it's back. I've reinstalled my VS 2022 and this did not help either. A pecularity of our setup is that we have downgraded System.Memory first to 4.5.2 (due to problems with SQLite - praeclarum/sqlite-net#1074) and then to 4.5.0 (due to problems with SignalR - #15311) but gesture recognizer had not worked before. Microsoft Visual Studio Enterprise 2022 Installed Version: Enterprise .NET Core Debugging with WSL 1.0 ADL Tools Service Provider 1.0 ASA Service Provider 1.0 ASP.NET and Web Tools 2019 17.1.363.30963 ASP.NET Web Frameworks and Tools 2019 17.1.363.30963 Azure App Service Tools v3.0.0 17.1.363.30963 Azure Data Lake Tools for Visual Studio 2.6.5000.0 Azure Functions and Web Jobs Tools 17.1.363.30963 Azure Stream Analytics Tools for Visual Studio 2.6.5000.0 C# Tools 4.1.0-5.22165.10+e555772db77ca828b02b4bd547c318387f11d01f Common Azure Tools 1.10 Extensibility Message Bus 1.2.6 (master@34d6af2) Fabric.DiagnosticEvents 1.0 Microsoft Azure Hive Query Language Service 2.6.5000.0 Microsoft Azure Service Fabric Tools for Visual Studio 17.0 Microsoft Azure Stream Analytics Language Service 2.6.5000.0 Microsoft Azure Tools for Visual Studio 2.9 Microsoft JVM Debugger 1.0 Microsoft Library Manager 2.1.161+abc97ecc7d.RR Microsoft MI-Based Debugger 1.0 Microsoft Visual Studio Tools for Containers 1.2 Mono Debugging for Visual Studio 17.1.10 (65f98f5) NuGet Package Manager 6.1.0 Razor (ASP.NET Core) 17.0.0.2206201+62a2c1d6162f828801565a7ca26d9d48b810a05b Snapshot Debugging Extension 1.0 SQL Server Data Tools 17.0.62203.25080 ToolWindowHostedEditor 1.0 TypeScript Tools 17.0.1229.2001 Visual Basic Tools 4.1.0-5.22165.10+e555772db77ca828b02b4bd547c318387f11d01f Visual F# Tools 17.1.0-beta.21610.4+07b5673e4f2fa7630e78abe37f16b372353a7242 Visual Studio Code Debug Adapter Host Package 1.0 Visual Studio Container Tools Extensions 1.0 Visual Studio IntelliCode 2.2 Visual Studio Tools for Containers 1.0 VisualStudio.DeviceLog 1.0 VisualStudio.Foo 1.0 VisualStudio.Mac 1.0 Xamarin 17.1.0.329 (d17-1@bc74cf0) Xamarin Designer 17.1.0.87 (remotes/origin/main@d50fb5635) Xamarin Templates 17.1.8 (590388a) Xamarin.Android SDK 12.2.4.3 (d17-1/fc1125e) Xamarin.iOS and Xamarin.Mac SDK 15.8.0.5 (cc19b50de) |
@jfversluis 17.2 seems to work fine. We'll see if it stops after some deployments. |
I am on a Macbook pro (intel) Visual Studio for Mac 17.6.7, Also tried Using VS 2022 on Virt Windows, this problem occures when in development, and also in production app, but only for the Community Toolkit EventTo Command behavior on our radio buttons. Everything else seems to be fine |
This issue has been moved from a ticket on Developer Community.
[regression] [worked-in:VS 2019]
Exactly as the title says. The app deploys and runs, however any controls using gesture recognizers do not respond to taps.
I am deploying to a USB-connected iPhone. It works fine on Android.
Some example code:
Original Comments
Feedback Bot on 11/17/2021, 00:01 AM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Graeme Vincent on 11/17/2021, 04:50 AM:
I think I need to point out that the gesture recognizers do work when I deploy to an iPhone connected to a Macbook.
That deployment has it’s own new set of problems which I have logged in another ticket.
Luke Sullivan on 11/18/2021, 09:43 PM:
I’m having the same problem. This is a major hinderance to our development schedule. Any workaround or solutions would be great! Thank you!
Luke Sullivan on 11/19/2021, 10:45 AM:
I would also like to point out that any iOS 15 device stopped deploying on vs 2019 as well. The workout fix was to take files from vs 2022 to allow vs2019 to then be able to deploy again. This solved that issue but now the gesture recognition doesn’t work in vs 2019 16.11.7 either. This is not restricted to vs 2022 v17.0.1
Original Solutions
(no solutions)
The text was updated successfully, but these errors were encountered: