I've migrated a settings page from Xamarin Forms ListView to CollectionView. All is working on iOS, but nothing is rendered on macOS.
I downgraded Xamarin Forms to 4.7 and pushed it all of the way up to the current preview of 5.0.0.1829-pre6. I've searched the source on git, and I can't even find a renderer for CollectionView. My searches on the web come back with nothing specific.
Is CollectionView supported on macOS? If not, what is the roadmap for support?
As of the current production release (4.8.X), 'CollectionView' is not supported on macOS, it is supported on the following platforms:
iOS
Android
UWP
There is no timeline for official support but I would hope it would become available in 5.X since that version will go into LTS when MAUI takes over. I checked the Xamarin GitHub repo and couldn't find an issue so I raised one for macOS support for CollectionView. Going to the repository is the best way to keep updated, if you show your support they are more likely to do the work 😊
Related
I have an app produced in Xamarin Forms and already published on the iOS AppStore. I recently updated the app and when I published it, it was uploaded to the AppStore with no images, tab bar icons, custom font that I had been using, etc. I have been investigating this for a couple of days but cannot come to a conclusion as to why this is happening. When debugging, everything shows as expected. I've even published an Ad-Hoc version of the build and everything is showing as expected with the Ad-Hoc version too.
There are also no issues with the android version on Google Play, so this seems to be happening specifically with the iOS version when being released/distributed to the AppStore.
Any help or suggestions would be greatly appreciated.
I've been testing my Xamarin app on IOS 14 beta 5, and I saw that there is a new privacy feature, where you can control what photos to share with your app. I am using an UIImagePickerController to display the photos, but right now I get all photos(even though I selected only some to be used by my app), and when trying to select one that was not in my selection, the app crashes.(PHImageManager.DefaultManager.RequestImageData return back wiht error code -1 in this case)
My question is, will there be some new features in the next Xamarin iOS framework to support this functionality?
Because I've been reading on the IOS developer forum that they are planning to have a new PHAuthorizationStatus-> PHAuthorizationStatusLimited, and maybe based on this status, we could filter our pictures.
Or is there currently a way to filter the photos I present on my UIImagePickerController?
Thanks
Apparently, in Xamarin.iOS 13.99.0, they introduced the new status: PHAuthorizationStatus.Limited, and also a new type PhotosUI.PHPickerViewController(since UIImagePickerController is obsolete, we will need to use the new PHPicker ).
More details on added or changed types are found here:
https://learn.microsoft.com/en-us/xamarin/ios/release-notes/api-changes/ios-13-20-2-13-99-0
If anyone needs to use this version of Xamarin.IOS, they can find it in Visual Studio->"Check For Options"->"Xcode 12 Preview" (Visual Studio 2019 For Mac).
Maybe someone will find this useful.
I am trying to add Lottie animations to my project.
So far I've only tested on android and I got it working.
Now I'm also trying to add them to my UWP app but I can't find a guide on how to do this.
There is this link that tells me lottie is supported on UWP.
And this post and (probably as a reaction) this post suggests it is possible within xamarin forms uwp.
I can't find a clear reference (or a tutorial) online if this is supported for Xamarin.Forms UWP projects. I'm mainly in doubt because I'm not sure if the Xamarin.Forms.UWP 'flavor' is the same as a 'normal' UWP application.
I could really appreciate a nudge in the right direction.
I think it has something to do with this bug.
Although this sample with an older version (2.5.4) was not built with "support" for UWP
I did get it working by adding the resources to the root dir and setting the build action to Content.
Downgrading the library in my own project to 2.5.4 fixed the problem for me.
I am working on an app that has iOS and tvOS versions. After the update to Xcode 11 the Branding Assets for the tvOS version started to glow in red. It seems that Xcode can't find them. I tried making a brand new project for tvOS and the result is the same!
After contacting the Apple support they confirmed that this is a bug and said that they are working on it. However a lot of time passed since then ...
I am writing this question to see, if other people have bumped into this problem and, if someone has found a workaround.
This bug actively prevents me to release new versions of the tvOS app via Xcode 11+.
I will write here if Apple responds with a fix for the problem, so other people may know, if a solution has been made available via the official channels.
Same here...
Setting the "Asset Catalog App Icon Set Name" in Build Settings manually did the trick for me (App Icon Source still shows up in red, but the icons are being used now).
Build Settings
Assets
Warning still present
PS: Also I removed the following lines from Info.plist. Not sure what actually solved the issue.
< <key>CFBundleIcons</key>
< <dict/>
< <key>CFBundleIcons~ipad</key>
< <dict/>
The problem was fixed in Xcode 11.3. The UI no longer glows red as shown in the question above.
I just recently downloaded the latest public release of Xcode (6.3) and I noticed the storyboard for my app is now low res on my Retina MacBook Pro. Images, text and standard UI elements all appear blurry. On the actual device everything looks fine and code still looks sharp its just while working in the Interface Builder.
Has anybody else noticed this and figured out a way to fix it? This is happening to me in both Swift and Objective-C projects including in Apple's sample projects (Master-Detail Application and etc).
I submitted this as a bug report, and Apple responded by saying that it is the desired appearance. They did not give an explanation, that was all they said.
It appears to be related to a bug in the newest iOS SDK, and as a workaround, they've forced Interface Builder to render everything at 1x. Currently, there doesn't seem to be any solution to this annoying problem other than to wait.
Just installed Xcode version 6.3.2 and this issue appears to have been fixed.
Have you tried re-installation of the same version? That helped once.
Alternatively, can upgrade to newer version, too.