My app is rejected from iOS review.
And It says that app crashed in only iPad.
I test with iPhone and iPad (5th generation) same as tested device in review, it works fine.
But I can't read crash report.
Can you give me some advice regarding what makes my app crash only in iPad?
crash report
I just suspect that I remove some cache in resume cycle of flutter app in main.dart.
@override
void deactivate() {
removeDiaryRankingCache();
super.deactivate();
}
@override
void didChangeAppLifecycleState(AppLifecycleState state) {
super.didChangeAppLifecycleState(state);
if (state == AppLifecycleState.resumed) {
updateLastVisit();
removeDiaryRankingCache();
}
}
And this removeDiaryRankingCache() takes so much time and it is over allocated time to launch app in iPad or use so much memory over allocated storage of iPad..?
Please help me in any way.
This is a dedicated space for developers to connect, share ideas, collaborate, and ask questions. Introduce yourself, network with other developers, and join us in fostering a supportive community.
Post
Replies
Boosts
Views
Activity
Hey, I have been working on the app that implements both Content Filter Providers and DNS Proxy for custom network security app. However, I would like to display traffic logs from Content Filter. What's the best way to do that?
I know that it works with UserDefaults under shared container with App Group. But I am not sure that it's the best approach for storing data that is constantly changing. I also tried to use CoreData with:
FileManager.default.containerURL(forSecurityApplicationGroupIdentifier: appGroup)
But I receive error that "The file couldn’t be saved because you don’t have permission., ["reason": No permissions to create file; code = 1]" because my FilterDataProvider has access to CoreData model.
Hello,
My system is a 2020 M1 Macbook Air running MacOS 15 Beta 7
Without going into too much details, I ran "sudo chown -R user1 /" and allowed it to run through-- some files and folders didnt get affected due to permissions but for the files that got their permissions changed--I cant do basic things when logged in as user2 or the root user.
For example: sudo command with anything as the shell would hang, or another thing is the system would get stuck at almost half way into verifying whatever .dmg or .pkg I would be trying to install. A Get Info look at /usr/bin/sudo shows that the admin and everyone groups have no access so I think thats why I couldnt use sudo.
What options besides booting into recovery to reinstall do I have to remedy this? Because due to a faulty power button, the Macbook shuts down 5 seconds into the 10 required holding the button in order to get the startup options screen.
Is there any way I can repair the permissions? I have a Time Machine backup from a date before when I ran this command if restoring is the only thing that will work. Also worth mentioning is that I have Tinkertool System, Onyx, and CleanMyMac installed just incase I would need a 3rd party tool to fix this.
Cheers,
At what age should I try I am 15 years old
I created a new XCode project by cloning a working project and then changing the name from SafetyTalks to Insights everywhere I found it in the XCode interface. after doing so, everything built and was published without any issues many times. Several weeks later, when attempting to execute the following command:
xcodebuild -scheme ${scheme} archive -archivePath ${archiveFilePath}
in a script that has also been used successfully many times in the past is suddenly writing the archive to the path that includes the name of the other project. Finder instead of Insights. When the following command is executed:
xcodebuild -exportArchive -archivePath ${archiveFilePath} -exportPath ${exportsDirectory} -exportOptionsPlist scripts/ExportOptions.plist
I receive the following response:
2024-08-20 16:10:40.179 xcodebuild[91395:1849040] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path "/var/folders/c7/qf7lbb955yx4yd0w9wrwxfqjhyxryd/T/gov.ornl.finder.prod.intune_2024-08-20_16-10-40.177.xcdistributionlogs".
error: exportArchive: "Insights.app" requires a provisioning profile.
Error Domain=IDEProvisioningErrorDomain Code=9 ""Insights.app" requires a provisioning profile." UserInfo={IDEDistributionIssueSeverity=3, NSLocalizedDescription="Insights.app" requires a provisioning profile., NSLocalizedRecoverySuggestion=Add a profile to the "provisioningProfiles" dictionary in your Export Options property list.}
** EXPORT FAILED **
mv: rename /Users/l4e/Mobile/Apps/Temp/Exports/insights.ipa to /Users/l4e/Mobile/Apps/Temp/Exports/gov.ornl.insights.prod.intune-1.0.0.3.ipa: No such file or directory
cp: /Users/l4e/Mobile/Apps/Temp/Exports/gov.ornl.insights.prod.intune-1.0.0.3.ipa: No such file or directory
cp: /Users/l4e/Mobile/Apps/Temp/Exports/gov.ornl.insights.prod.intune-1.0.0.3.ipa: No such file or directory
I have reviewed every single place within the XCode GUI and have not found the name Finder anywhere. I also had another developer review it together and still the name Finder was not found.
I have also cleaned the Build folder and have rebuilt it many times without success. What I think may happening is that somewhere there may be the Finder value that is written in a file that is inaccessible to the XCode GUI.
I have researched this and tried many suggested fixes but so far none have resolved it. All comments and suggestions are welcome.
Apple App Store 审查委员会的电子邮件地址是什么?我们想上诉
The app is developed using react native. The issue is only in the iOS app but not in the Android. The app crashes when it is opened. And after the first crash, it will work if we try to open it again.
We do not know much about the cause of the crash as it is not replicated in debug mode.
Here is the app crash report we got from the test flight app.
Incident Identifier: 5E35C4DD-8CCC-43D3-A2B3-152277C9013E
Distributor ID: com.apple.AppStore
Hardware Model: iPhone13,1
Process: WATAMUKI_MOBILE [9673]
Path: /private/var/containers/Bundle/Application/DF3C370A-0AF0-482A-ABFC-4C926BD37605/WATAMUKI_MOBILE.app/WATAMUKI_MOBILE
Identifier: jp.watamuki.ios
Version: 9.7 (134)
AppStoreTools: 15F31e
AppVariant: 1:iPhone13,1:15
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Coalition: jp.watamuki.ios [2520]
Date/Time: 2024-08-16 16:24:12.0699 +0900
Launch Time: 2024-08-16 16:23:49.0526 +0900
OS Version: iPhone OS 17.5.1 (21F90)
Release Type: User
Baseband Version: 4.50.06
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: SIGNAL 6 Abort trap: 6
Terminating Process: WATAMUKI_MOBILE [9673]
Triggered by Thread: 21
Thread 21 name:
Thread 21 Crashed:
0 libsystem_kernel.dylib 0x00000001ee12b42c __pthread_kill + 8 (:-1)
1 libsystem_pthread.dylib 0x0000000201ecac0c pthread_kill + 268 (pthread.c:1721)
2 libsystem_c.dylib 0x00000001acfceba0 abort + 180 (abort.c:118)
3 libc++abi.dylib 0x0000000201de8ca4 abort_message + 132 (abort_message.cpp:78)
4 libc++abi.dylib 0x0000000201dd8e5c demangling_terminate_handler() + 348 (cxa_default_handlers.cpp:77)
5 libobjc.A.dylib 0x000000019cf41e2c _objc_terminate() + 144 (objc-exception.mm:496)
6 libc++abi.dylib 0x0000000201de8068 std::__terminate(void (*)()) + 16 (cxa_handlers.cpp:59)
7 libc++abi.dylib 0x0000000201de800c std::terminate() + 108 (cxa_handlers.cpp:88)
8 libdispatch.dylib 0x00000001acf15de8 _dispatch_client_callout + 40 (object.m:579)
9 libdispatch.dylib 0x00000001acf1d400 _dispatch_lane_serial_drain + 748 (queue.c:3900)
10 libdispatch.dylib 0x00000001acf1df30 _dispatch_lane_invoke + 380 (queue.c:3991)
11 libdispatch.dylib 0x00000001acf28cb4 _dispatch_root_queue_drain_deferred_wlh + 288 (queue.c:6998)
12 libdispatch.dylib 0x00000001acf28528 _dispatch_workloop_worker_thread + 404 (queue.c:6592)
13 libsystem_pthread.dylib 0x0000000201ec7934 _pthread_wqthread + 288 (pthread.c:2696)
14 libsystem_pthread.dylib 0x0000000201ec40cc start_wqthread + 8 (:-1)
Thread 21 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000
x4: 0x0000000201ded2c3 x5: 0x000000016e6c6810 x6: 0x000000000000006e x7: 0x0000000000000000
x8: 0xf72f9e93f4d9ff97 x9: 0xf72f9e929ab58f97 x10: 0x0000000000000200 x11: 0x000000016e6c6340
x12: 0x0000000000000000 x13: 0x00000000001ff800 x14: 0x0000000000000010 x15: 0x0000000000000000
x16: 0x0000000000000148 x17: 0x000000016e6c7000 x18: 0x0000000000000000 x19: 0x0000000000000006
x20: 0x0000000000008a17 x21: 0x000000016e6c70e0 x22: 0x0000000000000114 x23: 0x000000016e6c70e0
x24: 0x0000000300dc6868 x25: 0x0000000303998700 x26: 0x0000000000000000 x27: 0x0000000303998700
x28: 0x0000000000000000 fp: 0x000000016e6c6780 lr: 0x0000000201ecac0c
sp: 0x000000016e6c6760 pc: 0x00000001ee12b42c cpsr: 0x40001000
esr: 0x56000080 Address size fault
I am trying to make https request in swift, with identity created from certificate and key. My code look like this
To create the identity.
func loadIdentity(certificate: String, privateKey: String)-> SecIdentity? {
guard let certData = Data(base64Encoded: certificate, options:NSData.Base64DecodingOptions.ignoreUnknownCharacters) else {
print("Unable to decode certificate PEM")
return nil
}
guard let cert = SecCertificateCreateWithData(kCFAllocatorDefault, certData as CFData) else {
return nil
}
let addCertQuery: [String: Any] = [kSecClass as String: kSecClassCertificate,
kSecValueRef as String: cert,
kSecAttrLabel as String: "certificateLabel"]
let tag = "fedvfdvdf-tag".data(using: .utf8)!
_ = deleteCertificateAndKey(certLabel: "certificateLabel",keyTag: tag )
let certAddStatus = SecItemAdd(addCertQuery as CFDictionary, nil)
guard let pemKeyData = Data(base64Encoded: privateKey, options:NSData.Base64DecodingOptions.ignoreUnknownCharacters) else {
return nil
}
let sizeInBits = pemKeyData.count * 8
let keyDict: [CFString: Any] = [
kSecAttrKeyType: kSecAttrKeyTypeRSA,
kSecAttrKeyClass: kSecAttrKeyClassPrivate,
kSecAttrKeySizeInBits: NSNumber(value: sizeInBits),
kSecReturnPersistentRef: true
]
var error: Unmanaged<CFError>?
guard let key = SecKeyCreateWithData(pemKeyData as CFData, keyDict as CFDictionary, &error) else {
return nil
}
let addKeyQuery: [String: Any] = [
kSecClass as String: kSecClassKey,
kSecAttrIsPermanent as String: true,
kSecValueRef as String: key,
kSecAttrApplicationTag as String: tag
]
let privKeyAddStatus = SecItemAdd(addKeyQuery as CFDictionary, nil)
let getIdentityQuery = [
kSecClass : kSecClassIdentity,
kSecReturnData : true,
kSecReturnAttributes : true,
kSecReturnRef : true,
kSecMatchLimit : kSecMatchLimitAll
] as CFDictionary
var identityItem: CFTypeRef?
let status = SecItemCopyMatching(getIdentityQuery , &identityItem)
print("identityItem finished with status: \(String(describing: identityItem))")
print("status finished with status: \(status)")
guard status == errSecSuccess else {
print("Unable to create identity")
return nil
}
return (identityItem as! SecIdentity);
}
o make api request. Code is breaking in this function, around this lines let task = session.dataTask(with: request) { (data, response, error) in and let session = URLSession(configuration: .default, delegate: URLSessionPinningDelegate(identity: identity), delegateQueue: nil) For testing I removed identity and just used default URLSession, and request start giving response (although it was 401 but it was not crashing), so my guess is error is because of URLSession.
func makeAzureRequest(scopeId:String, registrationId:String, key:String, certificate:String, provisionHost:String, fileNameWithFolder:String, modelId:String, completion: @escaping (Result<String, Error>) -> Void ) throws {
guard let identity = loadIdentity(certificate: certificate, privateKey: key) else {
throw NSError(domain: "", code: -1, userInfo: [NSLocalizedDescriptionKey: "Unable to create identity"])
}
let session = URLSession(configuration: .default, delegate: URLSessionPinningDelegate(identity: identity), delegateQueue: nil)
print("session: \(session)")
guard let url = URL(string: "https://global.azure-devices-provisioning.net/\(scopeId)/registrations/\(registrationId)/register?api-version=2021-06-01") else {
throw NSError(domain: "", code: -1, userInfo: [NSLocalizedDescriptionKey: "Invalid URL"])
}
var request = URLRequest(url: url)
request.httpMethod = "PUT"
request.setValue("application/json", forHTTPHeaderField: "Content-Type")
request.setValue("utf-8", forHTTPHeaderField: "Content-Encoding")
let body = ["registrationId": registrationId]
request.httpBody = try? JSONSerialization.data(withJSONObject: body, options: [])
let task = session.dataTask(with: request) { (data, response, error) in
if let error = error {
completion(.failure(error))
} else if let data = data, let responseString = String(data: data, encoding: .utf8) {
completion(.success(responseString))
}else {
completion(.failure(NSError(domain: "", code: -1, userInfo: [NSLocalizedDescriptionKey: "Unknown error occurred"])))
}
}
task.resume()
}
to call function where api function is triggered.
@objc(AzureProvisionWithCertificate)
class AzureProvisionWithCertificate: NSObject {
@objc(provisionAndUploadFile:withRegistrationId:withKey:withCertificate:withProvisionHost:withFileNameWithFolder:withModelId:withResolver:withRejecter:)
func provisionAndUploadFile(scopeId:String, registrationId:String, key:String, certificate:String, provisionHost:String, fileNameWithFolder:String, modelId:String, resolve:@escaping RCTPromiseResolveBlock, reject:@escaping RCTPromiseRejectBlock) -> Void {
print("starting swift code here")
do {
try makeAzureRequest(scopeId: scopeId, registrationId:registrationId, key: key, certificate: certificate, provisionHost: provisionHost, fileNameWithFolder: fileNameWithFolder, modelId: modelId) { result in
switch result {
case .success(let responseString):
// Handle success, perhaps update the UI or process the response
case .failure(let error):
// Handle failure, perhaps show an error message to the user
}
}
} catch {
print("Failed to initiate request: (error.localizedDescription)")
}
}
}
And URLSessionPinningDelegate class look like this to SSL pinning.
import Foundation
import Security
class URLSessionPinningDelegate: NSObject, URLSessionDelegate {
var identity: SecIdentity
init(identity: SecIdentity) {
self.identity = identity
}
func urlSession(_ session: URLSession,
didReceive challenge: URLAuthenticationChallenge,
completionHandler: @escaping (URLSession.AuthChallengeDisposition, URLCredential?) -> Void) {
if challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodClientCertificate {
let credential = URLCredential(identity: self.identity,
certificates: nil,
persistence: .forSession)
completionHandler(.useCredential, credential)
} else {
completionHandler(.performDefaultHandling, nil)
}
}
}
I recently updated to Sonoma 14.6.1 because I read it will fix the issues with available print sizes. Apparently it hasn't. How the heck does something so simple just go missing? I am printing on a HP wide format printer and I cant print anything larger than 8 1/2 x 14. it is just ridiculous. Does anyone have a solution for this problem if you are having the same issue? Apple please advise or offer a fix. I know I am not the only one having this issue with no way to resolve it.
I am working on retrieving the FCM token and my implementation works perfectly on iOS 17. However, when I try the same code on iOS 15, I consistently receive a null value for the device token. Below is the relevant portion of my code. Do I need to change my implementation for lower iOS versions? It feels like this might be related to the App Tracking Transparency (ATT) permission. Any insights on why this might be happening or how to resolve it would be greatly appreciated.
const userlogin = async () => {
const deviceType = Platform.OS == 'ios' ? 'IOS' : 'ANDROID';
try {
let fcmToken = await AsyncStorage.getItem('fcmToken');
if (!EMAIL_REGEX.test(email)) {
showError('Please enter email');
updateState({isloading: false});
} else if (password?.length < 4) {
if (password?.length < 1) {
showError('Please enter password');
updateState({isloading: false});
} else {
showError('Password should be at least 6 characters long');
updateState({isloading: false});
}
} else {
let apidata = {
email: email?.toLowerCase(),
password: password,
deviceToken: fcmToken,
deviceType: deviceType,
};
actions
.Userlogin(apidata)
.then((res: any) => {
if (!res?.isProfileSetup && res?.tagsId?.length > 0) {
navigation.navigate(navigationString.PRESONALIZESCREEN, {
userData: res,
});
updateState({isloading: false});
} else if (
(!res?.isProfileSetup && res?.tagsId?.length == 0) ||
res?.tagsId?.length == undefined
) {
navigation.navigate(navigationString.HOBBIESSCREEN);
updateState({isloading: false});
} else {
updateState({isloading: false});
// showSuccess('Welcome!');
}
console.log(res, 'User has successfully logged in');
})
.catch((err: any) => {
!!err?.data && showError(err?.data);
updateState({isloading: false});
});
}
} catch {
updateState({isloading: false});
}
};
Hi, I'm wondering if someone can help with an RealityKit Apple Dev project that was downloaded from the Apple Dev site. I'm simply wanting to change the camera for capturing images from rear facing to the front facing camera. I'm not experienced at all with Xcode so I can't seem to work out how this may be done. Is anyone familiar with this project and may be able to assist?
The link is here: https://developer.apple.com/documentation/realitykit
Hey there everyone, I recently swapped over to the 18 beta on my iPad Pro. I'm trying to install Mullvad's DNS-over-HTTPS from GitHub (Google "mullvad encrypted-dns-profiles" and it should be near the top)
When downloading on my iPhone, it shows properly in settings that I just downloaded a profile and can install it. However on my iPad, nothing appears when I download the .mobileconfig profile. Since it isn't automatically finding the profile, is there a way to select the file and install it or am I missing a step?
Yesterday I did a reset of my Apple Watch Ultra 2 (I'm using the betas on my iPhone 15 Pro Max and Apple Watch) and when I start it is like they want to install the native apps but never downloaded and error appears, anyone know how to fix it? Thank you very much, I attach images. The installation never ends, I'm correctly connected to my iPhone and to the same wireless network. Only third party apps are installed like Outlook or Bitwarden.
So I bought an iPhone 11 yesterday and it shows iOS 18.0 however there is not beta profile. I dont want to be in a beta program. what should I do. have I been scammed with a wrong phone ? Please help really worried
Undefined Symbol: _swift_FORCE_LOAD$_swiftCompatibility56 When Building Flutter iOS App with CocoaPods
Development
I am encountering an error when trying to build my Flutter iOS app for the simulator using CocoaPods. The build fails with the following error message:
Error (Xcode): Undefined symbol: _swift_FORCE_LOAD$_swiftCompatibility56
Could not build the application for the simulator.
Despite following the recommended steps to resolve this issue, the error persists.
Environment
Flutter Version: 3.22.2
Xcode Version: 14.2.0
CocoaPods Version: 1.11.2
iOS Deployment Target: 15.0
Swift Version: 5.0
Steps Taken to Resolve the Issue:
Updated iOS Deployment Target to 15.0:
Modified Podfile to set platform :ios, '15.0'.
Updated Xcode project settings to set iOS Deployment Target to 15.0.
Cleaned and Reinstalled Dependencies:
Ran flutter clean.
Deleted Pods and Podfile.lock.
Ran pod install.
Verified Compatibility of Dependencies:
Checked all dependencies to ensure they are compatible with Swift 5 and iOS 15.0.
Modified Build Settings in Xcode:
Ensured Swift Language Version is set to 5.0.
Added $(inherited) to Framework Search Paths and Other Linker Flags.
Despite these steps, the issue persists. Any help or suggestions would be greatly appreciated.
Error Logs:
Error (Xcode): Undefined symbol: _swift_FORCE_LOAD$_swiftCompatibility56
Could not build the application for the simulator.
Thank you for your assistance!
Let me start by apologizing for the long read.. I am not an Apple Developer or Power Mac user per se but I am also not a beginner. I am desperate for a solution because I’ve hit a wall. Im sorry I cant attach a Etrecheck report because it doesn’t support my Mac OS 15 Beta 6 on a M1 Macbook Air.
… So once I changed my password ant root’s using the command, but many restarts later I would still use my old password to get in so I ignored. But a week later and after finishing up a Time Machine backup, neither my old or new password would get accepted on screen-lock. I’m not sure if the things I just mentioned are related but its definitely worth mentioning. The reason for my doubt is because I was able to log in to the Web GUI of Webmin remotely using my iPhone and my username and the password I changed the wee earlier; the same one that got me locked out of Mac user accout (I tried both old and new). Activating root from the Webmin panel allowed me to log in to my Macbook as root for the first time and went through the ame process as if it was a fresh install.
I coulnt understand what was going on at this point Why did TouchID and passwordA fail only a few days later when I decided to do this ***** move? Why only after I finished backing up? I waited for the account locked timer to finish a few times but it would be in vain because it would just restart the the temporary lock each time the timer hits 0 or when I restart.cEven when I tried to change my account password from the root account GUI or terminal, it would accept the root password I enter but nothing happens…What’s even weirder is that MacOS would not accept that password I always use on the occasion of adding a new user. Any admin task is ok except for when I try to add a new user!!! WHAT THE HELL?!?!
Regardless of what the causes for this are, the symptoms and how each one contradicts the other are very weird and illogical, at least for me.
Finally, and I regret to say, that booting into recovery isn’t an option because every time I try holding the power button maybe a second or two after the chime sounds and the ztApple logo appears. I started experiencing this symptom around 2 years and I scoured the internet for a solution or any other way I could get into recovery but it seemed like I was the only one on earth to experience this problem. The local Apple repair wanted $100 just for opening up the laptop and typing up a report, so I couldn’t justify paying that amount for something I didn’t exactly need at that time and was able to live my life without needing to get into recover mode which I still hope would be the case now… and that is why I am being this details because every time I try to search for my problem I find that booting into recovery mode is always the recommended step to diagnose my password/account lock password.
Some more notes in case it would help anyone identify the problem I am facing which I hope I didn’t make worse by being in the root account all this time which at the time of sending this post is almost 16 hours.
When I logged into root, I went through all the prompts you would get when starting an account for the first time but skipped everything including setting up TouchID and my Apple ID. However, I did later log in to my Apple ID in haste and got the message on my iPhone that a new device was being set up, but after looking into it, it seemed like nothing changed from my device list.
It hasn't been 24 hours logged in as root and besides all the weird stuff I', experiencing, Seqouia ihas become generally sluggish-- it hangs when I'm using everyday stuff like TextEdit, or when I try to go to the Advanced tab in Finder. The most unusual thing which I've already mentioned earlier is the password I have set for roo (System Administrator at the prompt) not getting accepted by the system when I try to add a new user when in all other scenarios that require System Administrator privileges.
I hope someone from the community can help me out, and once again I do apologize for the long read, but my intention was only to minimize the need for back and forth like most otherone-linee reports spanning several pages.
I am quite embarrassed by this because I don’t know what I was thinking when I tried changing my account password like that from the terminal, but then again I am only 90% sure that was the cause, as for the other 10% … it's a total mystery!!
Thank you.
Hi There, I am developing an apple wallet pass for an insurance company and i'm currently using the generic pass template. My question is, are there any restrictions from Apple on using any other pass type (such as coupon or store .,.etc) since they may be more suitable for what i am creating.
I am definitely not going to use a boarding pass , but will i be able to use anything else ?
thanks!!
List members: When I try to open a particular website in Sequoia 15.1 beta using Safari, instead of the site opening, Safari downloads an app, "login.action".
When I try to open this app I receive the error message, "App from unauthorized developer."
I've tried to open in the app in Security settings, without luck.
Would greatly appreciate any advice.
I am working on a simple app that communicates using APDUs as Apple opened up NFC and HCE Entitlement for the EU market. I got the entitlement for my developer account, I have the entitlements available in the NDEF and TAG values and also added proper AID value. Also added SKExternalPurchase and SKExternalPurchaseLink keys to the Info.plist. When I check the CardSession.isSupported and NFCReaderSession.readingAvailable they come out to be true. But when checking the CardSession.isEligible it's value is false. When checking the documentation for it, it simply says that
A property that indicates whether the current device supports card session functionality.
How can check the issue with current system?
Last night I tried recording a Voice Memo for my singing group, but for some reason the microphones were barely picking anything up. (Even with me snapping my fingers around the mics) I tried recording a video and the microphone at first was fine, but then the sound faded out almost till there was nothing. I am running the iPadOS 18.1 beta, so maybe that has something to do with it, but has anyone who is running the beta either on the same iPad or a different model run into the same problem? I tried doing some research to see if pages like 9to5Mac had reported any issues with the mics, but I couldn’t find anything.