Post

Replies

Boosts

Views

Activity

Reply to I can't use the word "*****", but adverts for prostitutes are OK?
I'm bored with this now. Constant streams of spam, surely easily filterable, yet nothing is done. Apple, don't you find this embarrassing? There is lots about this forum for you to be embarrassed about - the number of non-developer posts, the overwhelming proportion of questions that are not answered, the small number of knowledgable people posting useful replies, and so on. Many of those are things that you can't do much about, but surely solving the spam problem is within the capabilities of a multi-billion-dollar corporation.
Sep ’22
Reply to App Store price change on October 5, 2022
There is no way to synchronise your tier change with the price changes, so inevitably there will be a period of time when either the price is too low or too high. You need to decide whether too high or too low is preferable. Note that in the past Apple have not sent out emails when the price change actually happens, so you need to watch carefully. I have previously submitted a feature request asking for a way to synchronise a tier change with an announced price change, with no feedback from Apple. You might like to do that too. In general, it’s likely that the new prices won’t have the same price available as you were using before. You might get lucky though.
Sep ’22
Reply to How to assure that Apple has sent us payment for the previous month?
Is there any way to check in App Store Connect that Apple has sent us the payments for the previous months? I would expect to see "Paid" at the top right of the Payments and Financial Reports app store connect screen for those months only if the payment has actually been sent. For example, for July I see: September 1, 2022 Transaction ID: 1234567890 Paid I would expect it to say "carried forward" or something if the payment was not sent.
Sep ’22
Reply to Email from app_notification@apple.com - Phishing?
I opened a support ticket with Apple and ask them if it's legit, but no reply so far. In my experience, Apple Support cannot recognise whether their own emails are legitimate or not. And their "report phishing" email address does not reply. Most likely, it is legitimate if the reply address was @ apple.com (and not app1e.com etc. etc.). It's unlikely that a phisher would be able to intercept your reply to an @ apple.com address. Maybe post the email headers here and someone who knows a bit about email forensics will be able to advise.
Sep ’22
Reply to How to assure that Apple has sent us payment for the previous month?
Carried Forward They haven't paid you (but they haven't forgotten about the money). Is the amount due very small? There used to be a lower limit for payments; I don't know if that is still the case or what the amount is. On that same screen in App Store Connect, I see details of my bank account (name of bank and last few digits of account number) near the top left. Do you see that?
Sep ’22
Reply to App Store price change on October 5, 2022
if you’d like to retain your current price, you could apply your price change to go into effect on October 5th to minimize price changes. The email says "As early as October 5...", which I interpret as "at some date on or after October 5". Are you saying that you believe it means exactly October 5? The similar announcement in August 2021 was more vague, it just said "in the next few days".
Sep ’22
Reply to Can you check with @available if your iOS app is running on Mac?
The exact same binary runs on the Mac as on the iOS device when you use the “Designed for iPad” feature, so there is no way to cause your function to not be included. It is possible to do a runtime test. I forget exactly how, is it a property of UIDevice maybe? (edit: it’s the ProcessInfo thing you already know about.) Is there some reason why a runtime test doesn’t work for you?
Topic: App & System Services SubTopic: Hardware Tags:
Sep ’22
Reply to UIFont monospacedDigitSystemFont doesn't work
When I do this: UIFont* uifont = [UIFont systemFontOfSize: sz weight: UIFontWeightRegular]; NSLog(@"font attributes: %@",uifont.fontDescriptor.fontAttributes); I get: font attributes: {     NSCTFontUIUsageAttribute = CTFontRegularUsage;     NSFontSizeAttribute = 64; } When I change it to monospacedDigitSystemFontOfSize:, I get this: font attributes: {     NSCTFontFeatureSettingsAttribute =     (         {             CTFeatureSelectorIdentifier = 0;             CTFeatureTypeIdentifier = 6;         }     );     NSCTFontUIUsageAttribute = CTFontRegularUsage;     NSFontSizeAttribute = 64; } So presumably that "feature settings attribute" with values 0,6 is the thing that gives it monospaced digits. Question: is that documented somewhere? Now, what I do with that UIFont is: CTFontDescriptorRef descr = (__bridge CTFontDescriptorRef)uifont.fontDescriptor; CTFontRef font = CTFontCreateWithFontDescriptor(descr, sz, nullptr); (I do that, because I never found a way to ask for monospaced-digits at the Core Text level.) Now I look up the advances for the digits: char16_t digits[] = u"0123456789"; CGGlyph glyphs[10]; CTFontGetGlyphsForCharacters(font, (const UniChar*)digits, glyphs, 10); CGSize advances[10]; CTFontGetAdvancesForGlyphs(font, kCTFontOrientationHorizontal, glyphs, advances, 10); for (int i = 0; i < 10; ++i) { NSLog(@"digit = %d, advance = %f",i,advances[i].width); } and I get this: digit = 0, advance = 39.031250 digit = 1, advance = 28.593750 digit = 2, advance = 36.437500 digit = 3, advance = 38.093750 digit = 4, advance = 38.906250 digit = 5, advance = 37.656250 digit = 6, advance = 39.718750 digit = 7, advance = 35.218750 digit = 8, advance = 38.593750 digit = 9, advance = 39.718750 Those clearly aren't equal. What's going on here? Does Core Text support monospaced digits, or is it something that is added at the UIKit level? If Core Text does support it, do I need to do something to my CTFontDescriptor to get it? Or maybe I should be looking at something other than the advances?
Topic: UI Frameworks SubTopic: UIKit Tags:
Sep ’22
Reply to UIFont monospacedDigitSystemFont doesn't work
So presumably that "feature settings attribute" with values 0,6 is the thing that gives it monospaced digits. Question: is that documented somewhere? It turns out that 0 is kMonospacedNumbersSelector and 6 is kNumberSpacing, where are documented here: https://developer-rno.apple.com/fonts/TrueType-Reference-Manual/RM09/AppendixF.html#Type6 - not that the developer.apple.com search can find it.
Topic: UI Frameworks SubTopic: UIKit Tags:
Sep ’22
Reply to What focal length ARKit uses?
You probably need kCGImagePropertyExifFocalLenIn35mmFilm , rather than kCGImagePropertyExifFocalLength, if you want to try to interpret the value that you get back in a way tha is device-independent. (Or, maybe there is now an actual field-of-view angle property? There wasn't last time I looked at CGImages from PHPhotoLibrary.)
Topic: Spatial Computing SubTopic: ARKit Tags:
Sep ’22