So the problem is simply with displaying the image. I've created the same scenario in a test Xcode app that does nothing, although the complication image DOES display there.
#Deepvacuum mac code
As far as I can tell, my code in the swift complicationController is functionally the same as the Xamarin one, and the settings in the ist are the same, and the assets are the same. I've also tried every way in Xamarin code to create the UIImage (FromBundle, FromResource, etc.) but none of them work.
I will attach both the Xcode and the Xamarin projects. Not all the watch faces allow custom complication (apparently), but in each one that allowed access to this complication, it displays.Ģ.Ĭustomize one of the watch faces (i.e., Modular) and add the testComplication Complication. Go through the same steps with the Xamarin app. Var rimgTemplate = new CLKComplicationTemplateModularSmallSimpleImage() If (complication.Family = CLKComplicationFamily.ModularSmall) I can get an image displaying in the complication (like Tim said) using Java HotSpot(TM) 64-Bit Server VM (build 25.74-b02, mixed mode)Īndroid Designer EPL code available here: Java(TM) SE Runtime Environment (build 1.8.0_74-b02) Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin ProfilerĪndroid SDK: /Users/axenu/Library/Developer/Xamarin/android-sdk-mac_x86 Notice that the complication image never displays. RimgTemplate.ImageProvider = CLKImageProvider.Create(UIImage.FromFile("my_image")) Įntry = CLKComplicationTimelineEntry.Create(NSDate.Now, rimgTemplate) Īs long as `my_image` is a *BundleResource* in the WatchExtension project root. It does *not* work if the image is in the WatchApp project, nor if I use `FromBundle`. It does *not* work any images in xcassets.Ģ. On closer examination of the Xamarin project (*Show Package Contents* of bin/iPhoneSimulator/Debug/WatchApp.app), it appears that we are not building an **Assets.car** file in either the Watch App or Extension.Ī. In the WatchApp, the assets are just embedded directly into the. This makes things "seem" to work (the app icon is displayed) but I don't think it's the correct behavior.ī. In the WatchExtension, the assets I placed in the xcassets aren't there at all! This is definitely a bug. I placed the Assets.car from Xcode's output into the Xamarin WatchExtension project root (BuildType:BundleResource) and THEN the following code works as it should: To prove this further, I built your Xcode project attachment, opened it up and took out the Assets.car file it created in the. generate an Assets.car file via Xcode, and embed it manually until we've fixed everything RimgTemplate.ImageProvider = CLKComplicationTimelineEntry.Create(NSDate.Now, rimgTemplate) #Deepvacuum not grabbing subdirectories code It looks to me like we have a bug creating Assets.car files in both WatchApp and WatchExtension projects tho' - at least: we don't produce the same. app/.appex output as Xcode does for the same xcassets.
#Deepvacuum mac update
Update on Comment #11 - I've checked other watchOS 3 solutions (eg. #Deepvacuum not grabbing subdirectories update the WatchKitCatalog) and both the WatchApp and WatchExtension _have_ Assets.car files. Turns out, WatchApp and WatchExtension projects seem to *ignore* the Complication node in Assets.xcassets: So assume there's an issue specific to Complication xcassets. #Deepvacuum not grabbing subdirectories code.#Deepvacuum not grabbing subdirectories update.
0 kommentar(er)
