Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 02 2016 16:31
    @chamons banned @IfErrThrowBrick_twitter
Manuel de la Pena
@mandel-macaque
@rolfbjarne that is the conclusion we arrived
@rolfbjarne do I like it.. not really, but is the only way
:confused:
Julio César Rocha
@JunielKatarn

Hi.
Does anybody know how to set up a Xamarin Forms app to run on macOS 10.9?

xamarin/xamarin-macios#8556

Sören Nils Kuklau
@chucker
XF is barely running on modern macOS, let alone a release that's seven years old
the system requirements you cite are for Xamarin.Mac, not Xamarin Forms
as your link to contentViewController shows, that's a new API starting in 10.10. my guess is XF doesn't depend on it too much, so you can probably make a fork and possibly a PR to make it compatible to work without contentViewController, but my money is on it isn't worth it — Xamarin Forms on macOS is in preview, supporting it isn't a high priority, and supporting rather old macOS at this point definitely isn't a priority
Julio César Rocha
@JunielKatarn

That's too bad. I hope the XF team will at least acknowledge this and state the minimum supported version clearly.
That said, I tried my app in macOS 10.10, and it still crashes, but the offending selector IS supported in that version.

I'll follow up in a new GitHub issue.

Sören Nils Kuklau
@chucker

state the minimum supported version clearly

XF on macOS isn’t supported at all; it’s in preview.

Julio César Rocha
@JunielKatarn
Yeah, I should have said "current targeted".
Sören Nils Kuklau
@chucker
Hm, yeah, https://github.com/xamarin/Xamarin.Forms/wiki/Platform-Support should list per-platform requirements and doesn’t
Julio César Rocha
@JunielKatarn

Neither does the per-platform "Report".
I did find something useful in the .NET AppKit docs:
https://docs.microsoft.com/en-us/dotnet/api/appkit.nssplitviewitem.minimumthickness?view=xamarin-mac-sdk-14

There seems to be an annotation declaring the supported OS version explicitly.

Do you know who owns the AppKit .NET projection, and specifically, the ObjCRuntime types?

Rolf Bjarne Kvinge
@rolfbjarne
For issues with the AppKit bindings, or in the ObjCRuntime namespace, you can file bugs in https://github.com/xamarin/xamarin-macios/issues
gonzobrains
@gonzobrains

Hi. First time visitor here. I'm dead in the water with trying to open storyboards right now. Originally my error was due to the render timing out. I upgraded to VS 2019 and now I get

"An error occurred while initializing the frame's content
System.ArgumentException: 'ZoomMenu_100 ' is not a valid value for property 'Name'."

I upgraded to VS 2019 Preview (which is supposed to fix this) but still get the error. What can I do now?

Brandon Blue
@DarkBlue_X2_twitter
Hello, does Mono currently work with MacOS Catalina 10.15.4?
Sören Nils Kuklau
@chucker
sure
Brandon Blue
@DarkBlue_X2_twitter
Can't figure out how to get it to work for the life of me
Sören Nils Kuklau
@chucker
i have Mono 6.12 on here
installed via Visual Studio for Mac
Brandon Blue
@DarkBlue_X2_twitter
So I downloaded the Visual Studio .pkg in my Downloads folder
when I right click to open I get this message
The operation couldn’t be completed. (com.apple.installer.pagecontroller error -1.)
Is this the correct installer file?
MonoFramework-MDK-6.8.0.123.macos10.xamarin.universal
Sören Nils Kuklau
@chucker
6.8 sounds old, i think?
Brandon Blue
@DarkBlue_X2_twitter
It seems to be the most updated one?
Sören Nils Kuklau
@chucker
hrm
Brandon Blue
@DarkBlue_X2_twitter
Sören Nils Kuklau
@chucker
in any case, even 6.8 should work in Catalina
but updating Visual Studio should give you a newer one
can you right-click, Open With, and pick Installer there?
Brandon Blue
@DarkBlue_X2_twitter
yep
Sören Nils Kuklau
@chucker
and that gives you the same error?
Brandon Blue
@DarkBlue_X2_twitter
Yeah, I'm gonna try to restart again and see if it helps.
Alexander Köplinger
@akoeplinger
maybe also try redownloading the .pkg, maybe it was damaged
Sören Nils Kuklau
@chucker
is the package running from inside a disk image? or the downloads folder?
gonzobrains
@gonzobrains
I'm curious. Why are you guys updating these packages individually? Is this recommended over just downloading updates through Visual Studio?
Alexander Köplinger
@akoeplinger
no it's a standard .pkg so it runs with Apple's installer component
if you're using VS for Mac then yeah I'd recommend to use what it downloads
Sören Nils Kuklau
@chucker
also, do you by any chance have System Preferences → Security & Privacy → General → Allow apps downloaded from set to only App Store?
gonzobrains
@gonzobrains
I see. But we often have problems with the toolchain breaking down, so as a last resort should we download from here?
Sören Nils Kuklau
@chucker
@akoeplinger right… but something is either screwy about the setup, or it's an obscure macOS bug. or indeed just a broken download. either way, pretty poor error reporting on Apple's part
Alexander Köplinger
@akoeplinger
I agree :smile:
gonzobrains
@gonzobrains
Also, can anyone recommend how to properly troubleshoot the toolchain? Right now, I use ad-hoc methods like checking all the logs on my Windows machine and the Mac build server, close apps, restart, pray. I'd like to find a more formal solution.
Sören Nils Kuklau
@chucker
that sounds about right D:
gonzobrains
@gonzobrains
And is there a way to have multiple SDKs on the same Mac build machine? It seems like any time there is a change our remote Windows PC has to update it. If that's the case, then each developer sharing the Mac has to all have the same setup. It would be fine to do so if everything is stable but if something breaks then we have to do the dance of updating the Windows PC, updating the Mac, switch to Preview channel if that doesn't work, then hope and pray some more.
Sören Nils Kuklau
@chucker
you can install multiple Xcode versions side by side
you can simply rename Xcode.app and/or place it in a different dir
gonzobrains
@gonzobrains
What do I have to do on the Window's side to make it recognize that?