Thanks for the reply. I was mistaking something - there is no need to declare 'stop' outside the closure! That said it doesn't explain the error. The following produces the same error, which I reckon is a compiler bug: import Foundation class Test {     func test() {         let stop:UnsafeMutablePointerObjCBool         stop.initialize(to: false)     } }

If you look at the documentation for UnsafeMutablePointer you will see that the memory pointed to has to be initialised, not the pointer itself and that the initialize method does this. This is confirmed by declaring stop as a var as in:     func test() {         var stop:UnsafeMutablePointerObjCBool         stop.initialize(to: false)     } This still fails the same way. I will report it as a compiler bug. I think that enumerateAttribute initialises it to false anyway, which is why this code isn't needed in the first place.

Ok, so how do you think the code should be written?

Thank you for this. No, I’m not used to using pointers in Swift. I try and steer clear of them. As I mentioned earlier these lines aren’t necessary anyway because emumerateAttribute deals with setting it up. Definitely a case of RTM (polite version).

I think the issue might be because I am using custom attributes. It is ok if none are present.

Thanks for your response. I had indeed set an incorrect attribute. One of those stupid mistakes you can stare at for hours and not see!!

Just found that the following code does the trick, it just needs amending to include traits:     class func preferredCustomFont(for fontFamily: String, andTextStyle textStyle: UIFont.TextStyle) - UIFont {         let systemFontDescriptor = UIFontDescriptor.preferredFontDescriptor(withTextStyle: textStyle)         let customFontDescriptor = UIFontDescriptor.init(fontAttributes: [             UIFontDescriptor.AttributeName.family: fontFamily,             UIFontDescriptor.AttributeName.size: systemFontDescriptor.pointSize // use the font size of the default dynamic font         ])         // return font of new family with same size as the preferred system font         return UIFont(descriptor: customFontDescriptor, size: 0)     }

I have tried building documentation for the SlothCreator using Xcode 13 beta and Mac OS Monterey beta and it doesn't open the documentation window (as per the demo). It just opens the Developer Documentation window. I guess that the developers have a later version of Xcode to be released rsn.

After much experimenting and googling I came across the answer to this. The answer is as follows: <key>UTExportedTypeDeclarations</key> <array> <dict> <key>UTTypeConformsTo</key> <array> <string>public.data</string> </array> <key>UTTypeDescription</key> <string>Writing Shed Data</string> <key>UTTypeIconFiles</key> <array> <string>writingshed.png</string> </array> <key>UTTypeIdentifier</key> <string>www.writing-shed.comuk.Writing-Shed.data</string> <key>UTTypeTagSpecification</key> <dict> <key>public.filename-extension</key> <array> <string>wsd</string> </array> </dict> </dict> </array> <key>UTImportedTypeDeclarations</key> <array> <dict> <key>UTTypeConformsTo</key> <array> <string>public.data</string> </array> <key>UTTypeDescription</key> <string>Writing Shed Data</string> <key>UTTypeIconFiles</key> <array> <string>writingshed.png</string> </array> <key>UTTypeIdentifier</key> <string>www.writing-shed.comuk.Writing-Shed.data</string> <key>UTTypeTagSpecification</key> <dict> <key>public.filename-extension</key> <array> <string>wsd</string> </array> </dict> </dict> </array>

Fixed the issue. My preview had no soundtrack. Given that the App Store doesn't play sound I saw no point.

MacAppStore

When I chose distribute I also chose sign automatically. This is a process I always follow. The binary uploaded ok the day before. Suddenly this.

I select the archive in the Xcode organiser and click Distribute App. Choose App Store connect click next choose upload chick next choose upload symbols and manage version number 7 click next 8 Choose automatically manage signing 9. click next 10 Fails with Provisioning profile failed qualification/Profile doesn't include the selected signing certificate.

The problem is that 4+ is the only option available - the rest are dimmed out.

I clearly lost the plot!!