offloading

Since iOS 14, more and more users experience a severe problem: When they launch our app, it quits right after showing the launch screen, obviously even before executing one line of code. In some cases, offloading and re-loading the app can help in this situation, but not always. In iOS 13, the problem occurred in the same way, but offloading and re-loading always helped. This seems to be a licence problem and reinstalling is no option, because our app holds critical personal data that the user often did not backup. So what can we do in this situation?

When I'm debugging my VPN tunnel provider application on the iPhone device I found some error logs in the console: udp_validate_cksum_internal [C8.1:1] udp incorrect IPv4-UDP non-offload checksum 0xeaff ulen 1502 It only appears when I'm tuning the MTU to a bigger value for the NEPacketTunnelNetworkSettings. What does this message mean? Does it mean the inbound udp packet has a bad checksum and will it be dropped by iOS?

Hello everybody! In my app I allow the user to change TTS voices and English Alex voice is one of possible options. However, there are some cases when it's treated as available when it's actually not. It results in pronouncing the TTS utterance with another voice. To prepare the list of available voices I use next code: NSMutableArray *voices = [NSMutableArray new]; for (AVSpeechSynthesisVoice *voice in [AVSpeechSynthesisVoice speechVoices]) { tt[voices addObject:@{ tttt@id: voice.identifier, tttt@name: voice.name, tttt@language: voice.language, tttt@quality: (voice.quality == AVSpeechSynthesisVoiceQualityEnhanced) ? @500 : @300 tt}]; } To start the playback I use the next code (here it's simplified a bit): AVSpeechUtterance *utterance = [[AVSpeechUtterance alloc] initWithString:text]; utterance.voice = [AVSpeechSynthesisVoice voiceWithIdentifier:voice]; [AVSpeechSynthesizer speakUtterance:utterance]; Cases when AVSpeechSynthesisVoice returns Alex as available when it's not: The easiest way to reproduce it is

I’m with a major Canadian university, developing an app to help users plan for and respond to local hazards, like earthquakes and flooding. Since this is the kind of app you set and forget until an emergency occurs, and there’s a good chance internet access won’t be available to re-download the app once a disaster occurs, what can we do to help our users avoid or prevent offloading of the app? Encouraging users to disable offloading seems like overkill. What other options would you suggest to help avoid offloading in the first place? Thanks!

I have 2 EndpointSecurity apps. App1 is doing the heavy lifting and processes multiple events(ES_EVENT_TYPE_AUTH_EXEC, ES_EVENT_TYPE_AUTH_OPEN, ES_EVENT_TYPE_AUTH_RENAME, ES_EVENT_TYPE_AUTH_UNLINK, ES_EVENT_TYPE_NOTIFY_CLOSE, ES_EVENT_TYPE_NOTIFY_CREATE ). App2 is responsible for checking whether Full Disk Access is granted or not: int main(int argc, char * argv[]) { ttes_client_t *client; auto res = es_new_client(&client, ^(es_client_t *clt, const es_message_t *msg) { }); tt_exit(res == ES_NEW_CLIENT_RESULT_ERR_NOT_PERMITTED ? 0 : 1); } (please note that none of the apps is a System Extension). Sometimes when App1 is runing and App2 executes, the system hangs. After few days of investigation, it seems that starting a new es client (even without registering any messages) causes the system to block all operations until all the currently pending auth requests from other clients are answered. This makes it very hard to reason about the application. It also requires to basically offload everything to

I just updated my iPhone SE 2020 64 GB to iOS 14 beta 2 and now I have no storage left. I have found that the category “Other” is taking about 26 gigabytes of space. I have 63.2 gigabytes of space taken up of my 64 and I have offloaded as many apps as I can. Anyone have any idea what could be causing this? Thanks!