The Status block in the Loxone config does not show icon anymore in the Loxone visualization. The used Loxone Config is version 13.1.10.
Reason is, that version 13.1 of the Loxone app was not finalized (but was fixed in a further alpha version).
So this problem should be gone when the Loxone Config version and Loxone Loxone app is updated to the most actual version. The actual versions can be found on the manufacturer download page (https://www.loxone.com/dede/support/downloads/)
Related
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.
In my Mac OSX app Am loading HTML from local file system (file:// URL) but on OSX Catalina it show a blank white screen, it works in fine in previous Mac versions.
It works fine in Debug or Release mode so prob a setting when it get signed for AppStore submissions.
I've also had local file issues in the original 10.15 build release, I've "heard" it is fixed in build 19A603 (released yesterday 10-21-2019), but personally have not verified that...
Note: Other Xcode devs have also reported this issue on beta and production versions (i.e. not an Xamarin related issue)
Apple Developer Forums: https://forums.developer.apple.com/thread/120248
I use Xcode 10 and added all required stuff for DarkMode support. When I run the project on Mojave everything works. But when I archive and distribute the app using Xcode 10 on HighSierra, then my app doesn't appear in dark mode on Mojave. Shouldn't Xcode 10 archive Mojave compatible version anyway?
Possible reasons:
You are using command line to create the archive, but your toolchain is set to use Xcode 9
You are using Dark Mode specific assets in asset catalog. Dark versions of those assets can only be compiled using Mojave.
For some reason, the asset catalog created with Xcode 10 only contains the dark mode colors and images if Xcode is run on a macOS 10.14 Mojave system or newer! This means for full Dark Mode support it's not enough to just use Xcode 10, you must run Xcode on macOS 10.14 or newer.
The Cocoa APIs for Dark Mode can still be used, so you can compile an app supporting Dark Mode with Xcode 10 on macOS 10.13, but the asset support will be missing.
But use xcode9.1 it shows well.
It should be a bug of Xcode 9.2. Just use Xcode 9.1.
As for now, there are two ways:
move images from Assets.xcassets to bundle (thus loaded image from file instead of assets);
still use Xcode 9.1 till apple fixes the bug. (bug has been reported to apple)
I updated Appcelerator, and now when I relaunch, all of my modules that are listed have the yellow 'warning' icon, hovering over them says they aren't supported by the SDK, and clicking the 'Add' icon loads a blank list.
I also rolled back and its still broke. Anyone else have this issue?
You can rebuild your module with the latest Ti SDK then try to use. Also, if you use third party module then check their update version which is compatible with the latest version of Ti SDK.
http://docs.appcelerator.com/platform/latest/#!/guide/Extending_Titanium_Mobile
Hope this helps.