There are files that fail to decompress on Mac or iOS.
Even using open source for iOS, they all fail.
Clicking on the MacBook to open it fails.
However, some compression programs on Mac or PC will successfully decompress it.
Is there any way to forcefully open or decompress such a compressed file (Zip)?
I tried the Apple Archive method, but that method also fails with an error now.
(Personally, I would like to be able to force such a file through the Apple archive.)
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I have a few questions about files that are allowed to be backed up by setting isExcludedFromBackup to false .
Is it correct that the files allowed to be backed up are backed up by iCloud and iTunes sync?
Are the files allowed for backup always/periodically backed up to iCloud? Or does it only sync when the user manually backs up the device?
If the files allowed for backup are regularly backed up to iCloud, will there be a capacity issue? (User's iCloud capacity)
If there is issue 3 above, is it a good solution to add an option to the app so that users can turn it on/off?
I have a question about Apple in-app purchases.
If a user purchases a non-consumable item that has already been purchased again instead of restoring it, does the same effect as the restoration occur, or does a new payment incur expenses for consumers?
The app has a restore button and a process to restore.
There are users who sometimes fail to restore, and I am thinking of guiding them to purchase again if the repurchase has the same effect as the restoration.
Currently crashing like screenshots on iOS 15.7 devices.
What causes this error to occur?
Our app supports the minimum iOS version from iOS 11, 12.
Our app does not support multiple windows in UIWindowScene.
That crash occurs on all phonepads.
When transferring files from iPhone to Watch, if you run the app and try to transfer after updating the OS, the transfer may not be possible. (or transmission seems to be too slow)
Just completely close the app, restart it, and try again.
Does anyone know the cause or solution to this problem?
It happened after the last 17.5 update and today after the 17.5.1 update.
The app doesn't crash or anything, and it doesn't happen often, so I didn't send any feedback or anything, but it's strange.
Topic:
App & System Services
SubTopic:
General
Tags:
Watch Connectivity
WatchKit
watchOS
Apple Watch
Crash in Xcode code review
When you enable Enable Code Review in the upper right corner of Xcode, Xcode crashes or loads infinitely.
I don't think this problem existed in previous versions of Xcode, but it is very serious in the current version 15.4.
It doesn't crash in all parts of Code Review, but Xcode crashes or loads infinitely in certain parts.
I really hope this will be fixed in the next Xcode version.
It happens so often that I'm going crazy. Seriously
Especially if there are many or wide changes in the swift file, the crash occurs in that part.
Delete the Documents path of the app
Will the files or folders in the documentDirectory path or applicationSupportDirectory path disappear or be deleted when the OS is updated?
I know that sometimes all the files in the cachesDirectory path are deleted when the OS is updated or the device is rebooted.
Sometimes, users of my app report that all the files in the documentDirectory path or applicationSupportDirectory path are deleted or disappear, or all the files are deleted and initialized.
I thought that the files or folders in the documentDirectory path or applicationSupportDirectory path were not affected by the OS update, but am I wrong?
Crash occurs in @MainActor class or function in iOS 14
Apps built and distributed targeting Xcode 16 version swift6 crash on iOS 14 devices.
We create a static library and put it in our app's library.
Crash occurs in all classes or functions of the static library (@MainActor in front).
It does not occur from iOS / iPadOS 15.
If you change the minimum supported version of the static library to iOS 11, a crash occurs, and if you change it to iOS 14, a crash does not occur.
Is there a way to keep the minimum version of the static library at iOS 11 and prevent crashes?
Xcode SPM (Swift Package Manager) Error
I added the "Apple App Store Server Swift Library" library to Xcode using Swift Package Manager.
Both the project and target are set to iOS 14 or higher.
However, when I build after adding the library, an error occurs with the library.
A message appears stating that the target is set to iOS 12.
I'm using Xcode 26.0.1.
Even after adding it to all my projects, the build continues with the same error.
I've tried building the library from version 1.0.0 to the latest version, but the same error persists.
Even after completely cleaning the project and running it, the same error persists.
Does anyone know how to fix this?
After the iOS 15 update, the following process causes the app to die.
Go to the home screen while running the app
Completely quit by removing the background state of the app
Start by pressing the icon on the home screen
As soon as the app is opened in the state it was in when the previous home screen was moved, there is a symptom that the app dies.
There was no such symptom until iOS 14.
Is this symptom a bug in iOS 15 ? Or is there a new option for background state of apps in iOS 15?
Updated to Xcode 14.0 and built with iOS 16 device.
In purple it says "[Security] This method should not be called on the main thread as it may lead to UI unresponsiveness." A warning is displayed.
location is
@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {...
There is a part where it is difficult to know exactly which function it is because a warning is displayed at the location.
I also replaced the admob library with the latest version, but I have the same problem.
Does anyone know the cause of this issue?
I need help.
I am developing a function using Live Text.
(I used ImageAnalyzer and ImageAnalysisInteraction.)
When executed, the following error log is displayed and the Live Text Button is displayed but not clicked or highlighted.
That is, it does nothing.
[Unknown process name] Error: this application, or a library it uses, has passed an invalid numeric value (NaN, or not-a-number) to CoreGraphics API and this value is being ignored. Please fix this problem.
[Unknown process name] If you want to see the backtrace, please set CG_NUMERICS_SHOW_BACKTRACE environmental variable.
[api] -[CIImage initWithCVPixelBuffer:options:] failed because the buffer is nil.
Are there any possible causes and solutions for this not working?
Or is there a setting I'm missing in order to use LiveText?
Below is part of the code.
Changing preferredInteractionTypes to all types doesn't change anything.
UIImageViews are displayed by switching left and right through UIPageViewController and calling the LiveText function.
Task {
var analyzer:ImageAnalyzer? = ImageAnalyzer()
if analyzer == nil {
return
}
let configuration = ImageAnalyzer.Configuration([.text])
do {
let pAnalysis = try await analyzer!.analyze(image!, configuration: configuration)
DispatchQueue.main.async {
//interaction!.preferredInteractionTypes = .automatic
interaction.preferredInteractionTypes = .textSelection
//interaction!.preferredInteractionTypes = .dataDetectors
//interaction!.preferredInteractionTypes = [.textSelection, .dataDetectors]
//interaction.preferredInteractionTypes = [.textSelection, .dataDetectors, .automatic]
interaction.selectableItemsHighlighted = true
interaction.analysis = pAnalysis
interaction.setContentsRectNeedsUpdate()
}
} catch {}
analyzer = nil
}
I currently own an Apple Watch SE2 device.
However, when I try to debug from the watch to the actual device, the connection loss issue occurs all too often.
Once the connection is lost, it continues to try to connect in the Disconnected list on the Xcode "Devices and Simulators" screen and is in a loading state.
Very often, even when the connection is established and you are trying to start debugging, it drops out.
Xcode cannot debug properly on the actual device.
I later found out that the Apple Watch SE2 does not support 5.0 Hz Wi-Fi, only 2.5 Hz.
I think that might be the cause.
Is this phenomenon less likely to occur if you debug on an actual device such as a regular Apple Watch 7/8/9 or Ultra model?
In fact, if debugging is difficult with the Apple Watch SE model, I am wondering whether I should purchase an additional Apple Watch.
Or is there another way to improve this issue?
It would be nice if the Apple Watch could be debugged by connecting it to a Mac with an actual cable like the iPhone.
I am wondering if there is a way to disable and enable network debugging in Xcode.
In the past, debugging the watch using only Bluetooth with the iPhone in Xcode seemed to be more stable.
Except for the Watch, the iPad doesn't have any major issues with Wi-Fi debugging on the iPhone.
My app is for iOS (not a Mac app).
It can be installed and run on M1 Mac.
ProcessInfo().isiOSAppOnMac returns True .
In this case, is there any way to get the OS version information of the Mac device where this app is currently installed?
All APIs that get the current version information return the iOS version.
For example, Mac 12.0 returns iOS 15.
Mac 11.0 and Mac 12.0 both return to iOS 15.
And some APIs started in iOS 15 crash on Mac 11.0.
So we currently want to know how we can get the Mac OS version information of the actual device in the above case.
(Additionally, not Mac Catalyst.)
The app sells non-consumable in-app purchases.
I also checked to enable family sharing.
However, there are frequent cases where users share purchases using the family sharing function and fail when attempting to purchase or restore from a device of the shared account.
Or, if a user who received the sharing makes a purchase, it will not be processed as shared payment information, but will be paid with the payment registered with the Apple ID of the current device.
I used StoreKit2 and use Transaction.currentEntitlements to get payment info after purchase or restore.
However, non-consumable in-app purchase information that has been shared with the family does not arrive normally.
When I looked at the Storekit2 documentation, I know that there is nothing special handled or added in the API or code related to family sharing.
If I'm wrong on this part or if you know a good solution to this non-consumable payment - family sharing, please advise.
Topic:
App & System Services
SubTopic:
StoreKit
Tags:
In-App Purchase
App Store
StoreKit
App Store Receipts