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

iOS Debugger Indicates App Has Terminated Immediately #9056

Closed
Tracked by #14032
hunsra opened this issue Jul 29, 2022 · 63 comments
Closed
Tracked by #14032

iOS Debugger Indicates App Has Terminated Immediately #9056

hunsra opened this issue Jul 29, 2022 · 63 comments
Labels
area-tooling XAML & C# Hot Reload, XAML Editor, Live Visual Tree, Live Preview, Debugging not-regression p/1 Work that is important, and has been scheduled for release in this or an upcoming sprint platform/iOS 🍎 s/move-to-vs-feedback Tells automation to ask the person to use VS Feedback to report the issue s/triaged Issue has been reviewed s/try-latest-version Please try to reproduce the potential issue on the latest public version t/bug Something isn't working
Milestone

Comments

@hunsra
Copy link

hunsra commented Jul 29, 2022

Description

When using the iOS remote simulator in Visual Studio 17.3.0 Preview 5, after the initial use of the debugger, subsequent uses of the debugger fail to stay connected to the app, indicating "The app has been terminated", even though the app successfully launches and stays running in the simulator.

Repro project: https://github.com/hunsra/iOSDebugger.App

Steps to Reproduce

  1. Create a new .NET MAUI App.
  2. Choose the "iPhone 13 Pro Max iOS 15.5" simulator from the list iOS Simulators targets.
  3. Debug the app.
  4. Press the stop debugging button on the toolbar.
  5. Debug the app again.
  6. Observe the app launch in the simulator, but the debugger detach and report "The app has been terminated." in the Debug output window.

Version with bug

6.0.400

Last version that worked well

Unknown/Other

Affected platforms

iOS

Affected platform versions

iOS 15.5

Did you find any workaround?

If you close Visual Studio and re-open it, the debugger works once as described above.

Relevant log output

Build Log:
Build started...
1>------ Build started: Project: iOSDebugger, Configuration: Debug Any CPU ------
1>You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
1>Executing SayHello Task to establish a connection to a Remote Server. 
1>			Properties: 
1>				SessionId=b92a0820222943055e8a343c271a5ad24afb06e716c984bec440a9277f42317b, 
1>				Addresss=192.168.0.188, 
1>				SshPort=22, 
1>				TcpPort=50727, 
1>				User=randy, 
1>				AppName=iOSDebugger,
1>				VisualStudioProcessId=12564,
1>				ContinueOnDisconnected=False
1>Detected signing identity:
1>  Bundle Id: com.companyname.iosdebugger
1>  App Id: com.companyname.iosdebugger
1>Skipping analyzers to speed up the build. You can execute 'Build' or 'Rebuild' command to run analyzers.
1>iOSDebugger -> D:\Repos\iOSDebugger\iOSDebugger\bin\Debug\net6.0-ios\iossimulator-x64\iOSDebugger.dll
1>Optimizing assemblies for size, which may change the behavior of the app. Be sure to test after publishing. See: https://aka.ms/dotnet-illink
1>/usr/bin/mdimport bin/Debug/net6.0-ios/iossimulator-x64/
2>------ Deploy started: Project: iOSDebugger, Configuration: Debug Any CPU ------
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
Launching 'iOSDebugger' on 'iPhone 13 Pro Max iOS 15.5'...


Debug Log:
The app has been terminated.

Hot Reload Log:
17:05 47.75 iOSDebugger: Hot Reload session started
17:05 52.32 iOSDebugger: Hot Reload session complete


Xamarin Log:
Connection to 'mbp2017' completed successfully
The dotnet SDK is already installed. Version: '6.0.400-preview.22330.6'
dotnet validation completed
Sdk packs found: Microsoft.iOS.Sdk
The dotnet ios workload is already installed. Version: '15.4.430'
dotnet validation completed
Server Settings:
- mlaunch path: /Users/randy/Library/Caches/Xamarin/XMA/SDKs/dotnet/packs/Microsoft.iOS.Sdk/15.4.430/tools/bin/mlaunch
- Xcode version: 13.4
- Xcode path: /Applications/Xcode.app

Checking Xcode version compatibility...
Build properties for D:\Repos\iOSDebugger\iOSDebugger\iOSDebugger.csproj: VisualStudioProcessId: 12564, RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, SolutionPath: D:\Repos\iOSDebugger\iOSDebugger.sln, SolutionName: iOSDebugger, MessagingVersion: 15.4.430, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: iossimulator-x64, IsHotRestartBuild: False, _DotNetRootRemoteDirectory: /Users/randy\Library\Caches\Xamarin\XMA\SDKs\dotnet/, ServerSshPort: 22, ServerTcpPort: 50727, ServerUser: randy, ContinueOnDisconnected: False, ServerAddress: 192.168.0.188
SetSelectedDeviceAsync BEST Pixel 5 - API 31 (Android 12.0 - API 31)
Build properties for D:\Repos\iOSDebugger\iOSDebugger\iOSDebugger.csproj: VisualStudioProcessId: 12564, RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, SolutionPath: D:\Repos\iOSDebugger\iOSDebugger.sln, SolutionName: iOSDebugger, MessagingVersion: 15.4.430, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: iossimulator-x64, IsHotRestartBuild: False, _DotNetRootRemoteDirectory: /Users/randy\Library\Caches\Xamarin\XMA\SDKs\dotnet/, ServerSshPort: 22, ServerTcpPort: 50727, ServerUser: randy, ContinueOnDisconnected: False, ServerAddress: 192.168.0.188
Build properties for D:\Repos\iOSDebugger\iOSDebugger\iOSDebugger.csproj: VisualStudioProcessId: 12564, RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, SolutionPath: D:\Repos\iOSDebugger\iOSDebugger.sln, SolutionName: iOSDebugger, MessagingVersion: 15.4.430, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: iossimulator-x64, IsHotRestartBuild: False, _DotNetRootRemoteDirectory: /Users/randy\Library\Caches\Xamarin\XMA\SDKs\dotnet/, ServerSshPort: 22, ServerTcpPort: 50727, ServerUser: randy, ContinueOnDisconnected: False, ServerAddress: 192.168.0.188
Build properties for D:\Repos\iOSDebugger\iOSDebugger\iOSDebugger.csproj: VisualStudioProcessId: 12564, RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, SolutionPath: D:\Repos\iOSDebugger\iOSDebugger.sln, SolutionName: iOSDebugger, MessagingVersion: 15.4.430, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: iossimulator-x64, IsHotRestartBuild: False, _DotNetRootRemoteDirectory: /Users/randy\Library\Caches\Xamarin\XMA\SDKs\dotnet/, ServerSshPort: 22, ServerTcpPort: 50727, ServerUser: randy, ContinueOnDisconnected: False, ServerAddress: 192.168.0.188
Starting Simulator to launch App...
The Simulator has been started to launch App...
Build properties for D:\Repos\iOSDebugger\iOSDebugger\iOSDebugger.csproj: VisualStudioProcessId: 12564, RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, SolutionPath: D:\Repos\iOSDebugger\iOSDebugger.sln, SolutionName: iOSDebugger, MessagingVersion: 15.4.430, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: iossimulator-x64, IsHotRestartBuild: False, _DotNetRootRemoteDirectory: /Users/randy\Library\Caches\Xamarin\XMA\SDKs\dotnet/, ServerSshPort: 22, ServerTcpPort: 50727, ServerUser: randy, ContinueOnDisconnected: False, ServerAddress: 192.168.0.188
Build properties for D:\Repos\iOSDebugger\iOSDebugger\iOSDebugger.csproj: VisualStudioProcessId: 12564, RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, SolutionPath: D:\Repos\iOSDebugger\iOSDebugger.sln, SolutionName: iOSDebugger, MessagingVersion: 15.4.430, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: iossimulator-x64, IsHotRestartBuild: False, _DotNetRootRemoteDirectory: /Users/randy\Library\Caches\Xamarin\XMA\SDKs\dotnet/, ServerSshPort: 22, ServerTcpPort: 50727, ServerUser: randy, ContinueOnDisconnected: False, ServerAddress: 192.168.0.188
Build properties for D:\Repos\iOSDebugger\iOSDebugger\iOSDebugger.csproj: VisualStudioProcessId: 12564, RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, SolutionPath: D:\Repos\iOSDebugger\iOSDebugger.sln, SolutionName: iOSDebugger, MessagingVersion: 15.4.430, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: iossimulator-x64, IsHotRestartBuild: False, _DotNetRootRemoteDirectory: /Users/randy\Library\Caches\Xamarin\XMA\SDKs\dotnet/, ServerSshPort: 22, ServerTcpPort: 50727, ServerUser: randy, ContinueOnDisconnected: False, ServerAddress: 192.168.0.188
Build properties for D:\Repos\iOSDebugger\iOSDebugger\iOSDebugger.csproj: VisualStudioProcessId: 12564, RunConfiguration: Default, ArchiveOnBuild: False, ArchivePath: , IsAppDistribution: False, SolutionPath: D:\Repos\iOSDebugger\iOSDebugger.sln, SolutionName: iOSDebugger, MessagingVersion: 15.4.430, DeviceSpecificBuild: false, TargetiOSDevice: , _iOSRuntimeIdentifier: iossimulator-x64, IsHotRestartBuild: False, _DotNetRootRemoteDirectory: /Users/randy\Library\Caches\Xamarin\XMA\SDKs\dotnet/, ServerSshPort: 22, ServerTcpPort: 50727, ServerUser: randy, ContinueOnDisconnected: False, ServerAddress: 192.168.0.188
Starting Simulator to launch App...
The Simulator has been started to launch App...

Xamarin Hot Reload Log:
[5:05:41 PM]  (iOSDebugger) .NET 6 Project references .NET MAUI.
[5:05:41 PM]  (iOSDebugger) Starting Hot Reload session...
[5:05:42 PM]  XAML Hot Reload initializing...
[5:05:45 PM]  (iOSDebugger) Hot Reload: Initialized Agent.
[5:05:47 PM]  XAML Hot Reload Connected and Ready.
[5:06:01 PM]  (iOSDebugger) Stopping a Hot Reload session due to ExplicitlyEnded ...
[5:06:01 PM]  Stopped Hot Reload session.

VS bug #1747084

@hunsra hunsra added s/needs-verification Indicates that this issue needs initial verification before further triage will happen t/bug Something isn't working labels Jul 29, 2022
@Eilon Eilon added the area-tooling XAML & C# Hot Reload, XAML Editor, Live Visual Tree, Live Preview, Debugging label Jul 29, 2022
@pierre01
Copy link

pierre01 commented Aug 2, 2022

I have the same issue.

@jfversluis jfversluis removed the s/needs-verification Indicates that this issue needs initial verification before further triage will happen label Aug 24, 2022
@gmenaka
Copy link

gmenaka commented Sep 9, 2022

I have connect to local ipad and when app start gets an following error:
...
Loaded assembly: /private/var/containers/Bundle/Application/21B18619-86A4-4317-B9F5-390D3A1DA737/StressTracker.Client.app/System.Net.Http.dll [External]
Loaded assembly: /private/var/containers/Bundle/Application/21B18619-86A4-4317-B9F5-390D3A1DA737/StressTracker.Client.app/System.Net.Primitives.dll [External]
Loaded assembly: /private/var/containers/Bundle/Application/21B18619-86A4-4317-B9F5-390D3A1DA737/StressTracker.Client.app/System.Numerics.Vectors.dll [External]
Loaded assembly: /private/var/containers/Bundle/Application/21B18619-86A4-4317-B9F5-390D3A1DA737/StressTracker.Client.app/System.Net.Sockets.dll [External]
Loaded assembly: /private/var/containers/Bundle/Application/21B18619-86A4-4317-B9F5-390D3A1DA737/StressTracker.Client.app/System.Drawing.Primitives.dll [External]
Loaded assembly: /private/var/containers/Bundle/Application/21B18619-86A4-4317-B9F5-390D3A1DA737/StressTracker.Client.app/System.Private.Uri.dll [External]
The app has been terminated.

do we need any setting?

@Kremed
Copy link

Kremed commented Nov 13, 2022

I'm facing same issue ?
Any suggestions ?

Loaded assembly: /private/var/containers/Bundle/Application/04806506-C300-4FAA-8B16-2C3FB8BDE211/Mobile.app/Microsoft.iOS.dll [External]
Loaded assembly: /private/var/containers/Bundle/Application/04806506-C300-4FAA-8B16-2C3FB8BDE211/Mobile.app/System.Runtime.dll [External]
Loaded assembly: /private/var/containers/Bundle/Application/04806506-C300-4FAA-8B16-2C3FB8BDE211/Mobile.app/System.Collections.dll [External]
Loaded assembly: /private/var/containers/Bundle/Application/04806506-C300-4FAA-8B16-2C3FB8BDE211/Mobile.app/System.Runtime.InteropServices.dll [External]
Loaded assembly: /private/var/containers/Bundle/Application/04806506-C300-4FAA-8B16-2C3FB8BDE211/Mobile.app/System.Threading.Thread.dll [External]
Loaded assembly: /private/var/containers/Bundle/Application/04806506-C300-4FAA-8B16-2C3FB8BDE211/Mobile.app/System.Threading.dll [External]
Loaded assembly: /private/var/containers/Bundle/Application/04806506-C300-4FAA-8B16-2C3FB8BDE211/Mobile.app/System.Net.Http.dll [External]
Loaded assembly: /private/var/containers/Bundle/Application/04806506-C300-4FAA-8B16-2C3FB8BDE211/Mobile.app/System.Net.Primitives.dll [External]
Loaded assembly: /private/var/containers/Bundle/Application/04806506-C300-4FAA-8B16-2C3FB8BDE211/Mobile.app/System.Numerics.Vectors.dll [External]
The app has been terminated.

@Soap-141
Copy link

Soap-141 commented Nov 14, 2022

Same issue with iPhone.

@alamzaib-farooq
Copy link

Any solution?

@eshvatskyi
Copy link

eshvatskyi commented Dec 1, 2022

the same, 17.5 preview 1

@DanielMuhlig
Copy link

Same, except the app also terminates on the iPhone. The app runs fine without the debugger.

@Soap-141
Copy link

unoplatform/uno#10748

@AndreasReitberger
Copy link

Same here, app starts, splash is showing, then the app is terminated. If I start it manually from the phone then, it starts and works fine.
Any workaround so far?

@Soap-141
Copy link

None.

@rubiomiguel06
Copy link

I am also struggling with this issue. I cannot debug my app

@glihm
Copy link

glihm commented Jan 19, 2023

Same issue here, with a brand new .NET MAUI application with .NET7. Up up up!
The hard point is that we have no more logs to understand a possible cause.
(tested on a local iPhone and Simulator)

@npostma
Copy link

npostma commented Jan 20, 2023

Same issue here. App works fine in the simulator and testable via Testflight. But not via Remote debugging. Same message, no error log of some sorts.

@rubiomiguel06
Copy link

The only way I've found of debugging the iOS app was to use Visual Studio for Mac

@Eilon Eilon added the s/move-to-vs-feedback Tells automation to ask the person to use VS Feedback to report the issue label Jan 20, 2023
@ghost
Copy link

ghost commented Jan 20, 2023

Thanks for the issue report @hunsra! This issue appears to be a problem with Visual Studio, so we ask that you use the VS feedback tool to report the issue. That way it will get to the routed to the team that owns this experience in VS.

If you encounter a problem with Visual Studio, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks.

  1. Go to the Visual Studio for Windows feedback tool or Visual Studio for Mac feedback tool to report the issue
  2. Close this bug, and consider adding a link to the VS Feedback issue so that others can follow its activity there.

This issue will be automatically closed in 3 days if there are no further comments.

@peter-bozovic
Copy link

I'm having the same issue after upgrading to the latest VS 17.4.4 and Xcode 14.1 and the phone to the iOS 16.1.2

Unable to debug my iOS application which is very problematic 🥺

And the msftbot seem to close all these issues since it considers them related to VS, but we have no place to trace if any of these issues were able to be fixed, or if there are any workarounds ...
like: #11324

Looks like we'll have to ping this issue every 3 days to keep it open if we want to have any feedback !

@glihm
Copy link

glihm commented Jan 22, 2023

I'm having the same issue after upgrading to the latest VS 17.4.4 and Xcode 14.1 and the phone to the iOS 16.1.2

Unable to debug my iOS application which is very problematic 🥺

And the msftbot seem to close all these issues since it considers them related to VS, but we have no place to trace if any of these issues were able to be fixed, or if there are any workarounds ... like: #11324

Looks like we'll have to ping this issue every 3 days to keep it open if we want to have any feedback !

Agree with you @peter-bozovic.

Same version as yours for VS and iOS, I have then tried with VS community 2022 17.5.0 Preview 3.0 and it worked (on Windows) after:

  1. A first unsuccessful deployment.
  2. Unplugged the iPhone from my computer, and rebooted the iPhone.
  3. I tried to start the application BEFORE reconnecting the iPhone to the computer. The app crashed several times.
  4. Reconnecting the iPhone to the computer I was then able to, finally, deploy and debug correctly.

But it looks like a bit random, though...

@Martinedo
Copy link

I could find these two exceptions and logs which occurred right before the app crash. It is not wrote in the logs in every crash, because the apple main thread is also working with the RootViewController and it will crash the app sooner as the debugger stops at the exception in MAUI.

On the MAUI side in the UIApplication.Main(args, null, typeof(AppDelegate));:

**System.InvalidOperationException:** 'RootViewController cannot be null'

I think this is the cause of the crash. AppDelegate is extended from MauiUIApplicationDelegate which is not yet properly initialized and its property Window.RootViewController is null

On the iPhone device log:

Thread 0 crashed with ARM Thread State (64-bit):
    x0: 0x0000000000000004   x1: 0x0000000000000000   x2: 0x0000000000008b00   x3: 0x0000000000000000
    x4: 0x0000000000000000   x5: 0x00000000000000a1   x6: 0x0000000000000000   x7: 0x0000000000000000
    x8: 0x000000016db3e8a8   x9: 0x0000000000000000  x10: 0x0000000102cb0340  x11: 0x0000120000001202
   x12: 0x0000000000001200  x13: 0x0000000000000000  x14: 0x0000000000001200  x15: 0x0000120000001200
   x16: 0x0000000000000131  x17: 0x0000000229371d40  x18: 0x0000000000000000  x19: 0x0000000102cb0328
   x20: 0x0000000102cb0278  x21: 0x00000002242e17e0  x22: 0x0000000000000000  x23: 0x0000000000000000
   x24: 0x0000000000008b00  x25: 0x0000000000008b01  x26: 0x0000000000008c00  x27: 0x0000000102cb0000
   x28: 0x0000000000000001   fp: 0x000000016db3e920   lr: 0x000000021acd706c
    sp: 0x000000016db3e890   pc: 0x000000020a86e41c cpsr: 0x60000000
   far: 0x00000001028f0000  esr: 0x56000080  Address size fault

Thread 0 is the com.apple.main-thread

I think a workaround till MAUI fixes it could be to initialize the MauiUIApplicationDelegate.Window.RootViewController , but I dont know yet how and where to do it.

@samhouts samhouts added the p/1 Work that is important, and has been scheduled for release in this or an upcoming sprint label Jan 24, 2023
@peter-bozovic
Copy link

I got latest iPhone 14 for tests, and after various strange error messages, cleaning, deleting, alot of restarting of everything, it seem to work now.

Maybe the only info found in #11324 is true, and the older devices are simply not fast enough to load all assemblies before VS can attach the debuger, and iOS kills it while taking too long to load ...

On my previous iPhone 8 used for testing, app seemed to be killed after 15s of loading.
On the iPhone 14 it loads in around 10s and the debugger works ...

@DanielMuhlig
Copy link

Maybe the only info found in #11324 is true, and the older devices are simply not fast enough to load all assemblies before VS can attach the debuger, and iOS kills it while taking too long to load ...

That sounds plausible. I am using a iPhone 7 and it sometimes (rarely) successfully attaches the debugger. On my newer iPad it works all the time.

@Martinedo
Copy link

Im using iPhone SE and also seeing that it crashes in different time windows.

@glihm
Copy link

glihm commented Jan 25, 2023

Yes the watchdog is killing applications if they take too much time to start. Also, don't forget to disable the "Low Power Mode", where the watchdog is even shorter! This causes the app to be killed before the debugger even connects.

@jeromelaban
Copy link

We're still getting issues on relatively recent devices like iPhone 11, unfortunately.

@mattleibow
Copy link
Member

@jeromelaban @Eilon considering there's already a devdiv bug for this (https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1747084) is it expected to open another VS feedback issue that will ultimately end up being a xamarin/xamarin-macios issue?

This internal issue is closed now because there is no info on there. We are unable to reproduce so is likely a specific configuration or device version issue. In order to correctly investigate we need the logs that come with the report an issue feedback tool in the IDE as @mariaghiondea mentions above:

Go to the Visual Studio for Windows feedback tool or Visual Studio for Mac feedback tool to report the issue

1 similar comment
@mattleibow
Copy link
Member

@jeromelaban @Eilon considering there's already a devdiv bug for this (https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1747084) is it expected to open another VS feedback issue that will ultimately end up being a xamarin/xamarin-macios issue?

This internal issue is closed now because there is no info on there. We are unable to reproduce so is likely a specific configuration or device version issue. In order to correctly investigate we need the logs that come with the report an issue feedback tool in the IDE as @mariaghiondea mentions above:

Go to the Visual Studio for Windows feedback tool or Visual Studio for Mac feedback tool to report the issue

@BCSharp
Copy link

BCSharp commented Jun 1, 2023

This issue doesn't occur on Visual Studio for macOS

It also doesn't occur on Visual Studio (for Windows) if the device is plugged into the paired Mac and selected as "iOS Remote Device" from the run drop down menu. This is my current workaround.

If I have it plugged in directly to the Windows machine and attempt to run on "iOS Local Device", I get the same problem as everyone else here.

@roja300
Copy link

roja300 commented Jul 1, 2023

I am also having the issue. I tried to change from Xamarin to .net MAUI because of this. I have seen similar issues dating back to 2016. This is ridiculous.

Considering just completely rebuilding my app using flutter because of this.

@samhouts samhouts modified the milestones: .NET 8 Planning, .NET 8 GA Jul 12, 2023
@Zhanglirong-Winnie Zhanglirong-Winnie added s/triaged Issue has been reviewed s/try-latest-version Please try to reproduce the potential issue on the latest public version labels Jul 27, 2023
@ghost
Copy link

ghost commented Jul 27, 2023

Hi @hunsra. We have added the "s/try-latest-version" label to this issue, which indicates that we'd like you to try and reproduce this issue on the latest available public version. This can happen because we think that this issue was fixed in a version that has just been released, or the information provided by you indicates that you might be working with an older version.

You can install the latest version by installing the latest Visual Studio (Preview) with the .NET MAUI workload installed. If the issue still persists, please let us know with any additional details and ideally a reproduction project provided through a GitHub repository.

This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

@Zhanglirong-Winnie
Copy link

Verified this issue with Visual Studio Enterprise 17.7.0 Preview 4.0. Not repro on iOS platform with sample project.
iOSDebugger.App-master.zip

@ghost ghost closed this as completed Aug 3, 2023
@Soap-141
Copy link

Soap-141 commented Aug 8, 2023

Is the fix on 17.7.0 stable? Trying it and doesn't work right now.

@vassiliospallis
Copy link

vassiliospallis commented Aug 8, 2023

There is no fix. They didn't fix anything that corresponds to this ticket. They just closed the ticket with the flag "Try latest version".

@JordiCasas
Copy link

I found a 'half' workaround.

  1. Delete all breakpoints
  2. Deploy the app for a debug session
  3. Place desired breakpoints

Now breakpoints are hit and debugger works more or less, but I can't step over, need to place new breakpoints and continue (F5).

@ghost
Copy link

ghost commented Aug 22, 2023

Hello lovely human, thank you for your comment on this issue. Because this issue has been closed for a period of time, please strongly consider opening a new issue linking to this issue instead to ensure better visibility of your comment. Thank you!

@danroth27
Copy link
Member

@Eilon @jfversluis Should this be reactivated? It sounds like users are still hitting this problem. Uno is reporting it still as well with 17.7: unoplatform/uno#10748.

@Soap-141
Copy link

I guess... Still a big issue when it's a bigger app.

@mattleibow
Copy link
Member

This should be opened if it still is happening, but in the VS Feedback tool or in the macos repo.

@danroth27
Copy link
Member

@Soap-141 It sounds like you have a reliable repro for this. Do you want to go ahead and open the VS Feedback ticket and link it from here so that folks following this issue can find it?

@Soap-141
Copy link

@Soap-141 It sounds like you have a reliable repro for this. Do you want to go ahead and open the VS Feedback ticket and link it from here so that folks following this issue can find it?

Sure I can try tomorrow.

@Soap-141
Copy link

@danroth27 Did not have time to do it. Do you know if it's safe because I can't share logs from this project it's private.

@danroth27
Copy link
Member

@danroth27 Did not have time to do it. Do you know if it's safe because I can't share logs from this project it's private.

Logs are collected and uploaded by default, but you can opt out of this if you want. It will make it much more difficult to figure out what's going on though. It would be ideal if you can slim down your project to a minimal repro project that demonstrates the problem and that you can share.

Or if someone else following this issue has a reliable repro that they can share please go ahead and file your own VS feedback ticket. More data from more users helps.

@Soap-141
Copy link

@danroth27 Managed to find an easy way to reproduce it. Creating an issue right now.

@Soap-141
Copy link

Here, I used the VS feedback tool. https://developercommunity.visualstudio.com/t/iOS-Debugger-Indicates-App-Has-Been-Te/10453966 the recording and all attachments are not visible for you guys but I did provided them.

@ghost ghost locked as resolved and limited conversation to collaborators Sep 29, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-tooling XAML & C# Hot Reload, XAML Editor, Live Visual Tree, Live Preview, Debugging not-regression p/1 Work that is important, and has been scheduled for release in this or an upcoming sprint platform/iOS 🍎 s/move-to-vs-feedback Tells automation to ask the person to use VS Feedback to report the issue s/triaged Issue has been reviewed s/try-latest-version Please try to reproduce the potential issue on the latest public version t/bug Something isn't working
Projects
None yet
Development

No branches or pull requests