Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Mauro Agnoletti
    @mauroa
    It's a bit tricky. Maybe you can try installing an older iOS SDK from Xcode 11.4, so VS can pick up older simulators as well and hopefully that unblocks you. You can try that as a workaround while we investigate the issue
    IoTFier
    @IoTFier
    hmm .. sounds a long route for me ... will wait for you all ... thinking about it.. is there away to point to older simulators from VS ?
    any reg key for that ?
    I think that could also give us a good option to try iOS vN-1 ? What you say ?
    Mauro Agnoletti
    @mauroa
    To point to older sims you should have them available. And Xcode is responsible for that. Then, from VS you just need to play with the minimum deployment target fo your project
    IoTFier
    @IoTFier
    aah.. so Xcode deletes older simulator everytime we upgrade it ?
    Mauro Agnoletti
    @mauroa
    Well, the simulators are part of the Xcode installation, and the SDK is really heavy. If it keeps all the versions your machine will run out of space really quick and maybe you will not use old simulators at all
    In Xcode, if you go to Preferences -> Components, you can install older SDKs
    IoTFier
    @IoTFier
    can we install on deman versions ?
    Mauro Agnoletti
    @mauroa
    Yes, Preferences -> Components
    That's what I suggest so you let VS getting older simulators and see if that gets you unblocked
    IoTFier
    @IoTFier
    how do I control that ?
    from VS ?
    Mauro Agnoletti
    @mauroa
    From Xcode
    VS just picks up from the Mac what Xcode has for it
    Depending on the deployment target set on your project
    If you have 13.2 as minimum and Xcode has 13.2, 13.3, 13.4, it will pick them all. If you have 13.4 as minimum, it will pick only 13.4
    IoTFier
    @IoTFier
    got it.. is it the same way you can uninstall the older simulators too ?
    Mauro Agnoletti
    @mauroa
    if you install them and then want to uninstall, yes
    IoTFier
    @IoTFier
    but for that I will need to have all those simulators installed in XCode first right ?
    Mauro Agnoletti
    @mauroa
    Yes
    Just install the 13.3 SDK on Xcode
    And VS will pick the 13.3 simulators as well
    IoTFier
    @IoTFier
    this is great. I have a dedicated build machine and have couple 100 gb available .. so that's nota problem. How do I point those simulators to store on another hard disk (non ssd) ?
    IoTFier
    @IoTFier
    @mauroa - do I have to run those new simulators at least once on Mac before accessing it form VS ? When I am running my app , the older versions of the simulators are showing black screen
    Mauro Agnoletti
    @mauroa
    hmmm no that I know of, but you can try
    IoTFier
    @IoTFier
    just did it.. on mac it booted that first time and I could run a sample app from inside Xcode on the older 13.2.2 simulator... now will try it from VS
    yeeeeeeeeeeep ! my app works on 13.2.2
    so definitely there is a bug in x.ios against 13.4
    @mauroa - thank you so much. I owe you one.
    Mauro Agnoletti
    @mauroa
    Glad to know you got unblocked. We are currently investigating the 13.4 and XI 13.16 issue
    IoTFier
    @IoTFier
    another repeat bug in 16.5.2 is that when I press F5 .. the app builds but doesn't get deployed to the simulator on the first F5 click .. but it does on the subseuqent ones.. this was the issue earlier sometime back in Jan or last year
    IoTFier
    @IoTFier
    image.png
    @mauroa - got unexpected error while I was running Xamarin solution on both android and ios to use HotReload SxS
    attempt to reconnect throws another error
    image.png
    IoTFier
    @IoTFier

    @mauroa - got unexpected error while I was running Xamarin solution on both android and ios to use HotReload SxS

    This is error is becoming very frequent.

    IoTFier
    @IoTFier

    @mauroa - got unexpected error while I was running Xamarin solution on both android and ios to use HotReload SxS

    This is error is becoming very frequent.

    bounced both my pc (surface book 2) and mac mini .. now getting

    image.png
    IoTFier
    @IoTFier

    image.png

    Another one ..

    image.png
    IoTFier
    @IoTFier
    Hi @joj, @josegallardo - any one of you could have clue why am I facing the above error of failing to install the app on iphone simulator ?
    Mauro Agnoletti
    @mauroa
    Looks like an issue with the remote simulator. You can try to see if it works fine without the remote simulator (just to confirm the theory) or share the VS logs (Help > Xamarin > Zip Logs...) so we can check
    IoTFier
    @IoTFier
    Hi @mauroa - I will check it again and let you know. Thank you for your response.
    IoTFier
    @IoTFier
    Hi @mauroa , there is definitely something in the new fix that keeps breaking the remote connection with mac. Simulator gets disconnected during debugging session as well. I will be happy to provide you log in a secured manner if you give steps to product the required log and share it with you securely.
    Mauro Agnoletti
    @mauroa
    Let's start by getting all the Xamarin logs, by doing Help > Xamarin > Zip Logs... . That will include remote simulator logs so we can see what's going on with it.
    Also if something goes wrong with the debug session you can also include the content of the Debug output pane.
    IoTFier
    @IoTFier
    image.png
    where do I send those logs to you ?
    Mauro Agnoletti
    @mauroa

    So, If IDB also failed to start please attach the IDB.log from the Mac. Follow these steps:

    • Manually go to the Mac you tried to connect and look inside ~/Library/Logs/ for a Xamarin-{version} or Xamarin.Messaging-{version} folder. I recommend to order by Date Modified descending.
    • The format of the log files inside the folder are: {DateTime}.{VSProcessId}.{AgentName}.log
    • I recommend to validate that the logs are the expected ones by checking which is you current VS Process Id in Windows (for the VS session that is opened an that reproduced the bug) and seeing if that matches with the {VSProcessId} part of the log file names
    • If everything is correct please zip the logs of that folder
    You can send everything to maagno@microsoft.com|maagno@microsoft.com

    Andrii Kurdiumov
    @kant2002
    Hi, anybody know why iOS Local Device option do not available on Visual Studio (Win) and how I can troubleshoot that? iTunes see device just fine, and I can view logs from device inside VS.