3.2.x Bug Report / Feedback Thread
- Thread starter mikelove
- Start date
Shun
状元
Hello Mike,
I've just come across a bug that happened when I added a custom flashcard from a bit of Chinese text I selected while testing myself on a flashcard. Even though I have set a category to save the custom flashcard in, it will be saved in the "Uncategorized" area instead of the category I had set. The category was already set to the default Flashcards category when I entered the dialog. So I select Chinese text, tap on the "+" button, and add the following input:
After I tap Save, I find this card in Uncategorized.
If you can't reproduce the bug, I'd be happy to send you my flashcards database.
Thanks,
Shun
I've just come across a bug that happened when I added a custom flashcard from a bit of Chinese text I selected while testing myself on a flashcard. Even though I have set a category to save the custom flashcard in, it will be saved in the "Uncategorized" area instead of the category I had set. The category was already set to the default Flashcards category when I entered the dialog. So I select Chinese text, tap on the "+" button, and add the following input:
After I tap Save, I find this card in Uncategorized.
If you can't reproduce the bug, I'd be happy to send you my flashcards database.
Thanks,
Shun
Last edited:
We've had a few reports of this, will let you know if we have trouble reproducing it the next time we're doing an iOS bug fix update. (we're waiting a few weeks on that because we want 16.1 to be out in the field first, partly because it fixes some bugs in 16.0 that we'd rather not have to work around ourselves but would need to if we released an update built around the iOS 16 SDK)
jurgen85
榜眼
The font 硬笔行书 actually has pretty good traditional coverage, but it is missing some essential “variant” characters like 為, 強 and 絕. While this is obviously 方正’s problem (or ultimately a standardization problem), fortunately, its brother 硬笔楷书 has better coverage. I think using that as a fallback before 黑体 would look very natural.
Apple forced us to remove it - they now consider the APIs we were using to run a private on-device web server to be restricted / private APIs that developers are no longer permitted to use in their apps.
To be honest it was already kind of an unnecessary legacy feature, given that we now have AirDrop and "external files" and easy sharing from other apps - we added it all the way back in iOS 2.0 when it was actually really difficult to get files into an app any other way.
To be honest it was already kind of an unnecessary legacy feature, given that we now have AirDrop and "external files" and easy sharing from other apps - we added it all the way back in iOS 2.0 when it was actually really difficult to get files into an app any other way.
This appears to have worked, many thanks!
I don't use it a lot, but I can't find the "Upload / Download Files" screen (for transferring files over wi-fi). Has it disappeared? I see no mention of it on any app store release notes.
It was definitely there in 3.2.64, and the latest 3.2.70 still has a setting for assigning a custom port, yet I can't find the feature anywhere. Is this a bug or a quietly removed feature?
It was definitely there in 3.2.64, and the latest 3.2.70 still has a setting for assigning a custom port, yet I can't find the feature anywhere. Is this a bug or a quietly removed feature?
Quietly removed, but not by choice - Apple marked a couple of the relevant programming interfaces as private APIs (I guess not a lot of people trying to run web servers on phones anymore) and so we were forced to remove them.