Well, there is a bug in Apple’s MapKit since iOS 13.2, as the folks in developer community say: If you want to use non-Apple maps (e.g. OpenStreetMap®) occasionally tiles are not rendered although you supply the correct data in your sub-class of
MKTileOverlayRenderer. There seems to be no obvious systematic but if you scroll around the map you’ll soon find missing tiles. There seems to be no real fix for that problem and your app will not be notified if that happens; the delegate method
mapViewDidFinishRenderingMap(mapView:fullyRendered:) will always signal „
fullyRendered“ although tiles may be missing. Weiterlesen
Recently, I noticed that the newly introduced
fileExporter view modifiers in SwiftUI won’t work inside a
Menu view. It’s not a big deal to put the file modifiers outside of the menu, but it took quite a while for me to pin down the problem.
Well, that was harder than I thought. I was tired of waiting for Synology to update the WordPress version to the current one and started this little project to install the public version of WordPress on my Synology NAS and to migrate my website to that. Couldn’t be too difficult I thought. But it turned out that there were quite some obstacles to overcome; but finally, I succeeded, and I want to share my experiences with you.
Well, SwiftUI is certainly a big improvement on building maintainable, robust and nice user interfaces on iOS and macOS compared to the old MVC architecture (Massive View Controller) and the NIB (Next Interface Builder). But it is mainly a declarative framework and from the application developer’s point of view it’s sometimes hard to anticipate what is really going on behind the scenes and especially when its going to happen. There are situations where the promised behaviour doesn’t take place and I’ve already struggled hours for hours to look for a workaround.
.onAppear modifier seems to be problematic. It looks as if the supplied closure will be executed too early sometimes and the statements inside do not have the desired effect.
As quite a lot of people have noticed already (e.g. here) the Synology Drive Client 3.2.0 – 13258 Update has a problem. After the update it is crashing silently all the time on my Macs. The advice from the Synology support to re-install the Drive client from scratch may be constructive but is quite tedious if you have a lot of shares configured (as for me). A hint in the above mentioned forum lead to the solution.
Obviously the password of the stored connection to the Synology NAS is corrupt after the update. Since the Drive client crashes very soon after startup the best procedure to restore the correct password is the following: