SwiftUI List performance

I think the problem aren't Apple in this case.From one of your own post:No all you have to do is jailbreak the phone and get free in app purchases plug in and then you can get anything free that's not server verified before adding the purchase to the user account.If a phone are jailbroken, you can request on a app the purchase. Now, in Jailbreak, you have installed an app who when request a purchase, they doesn't send it to Apple, and send to your app an OK.I understand the problem here are the Jailbreak itself. Apple try to avoid it, but, there's a lot of people who try to mantain it.There's a lot of people who are scammed every day because Jailbreak, in form of downloads of the app without payment, or in-app purchases without payment. At first case, you cannot verify, because, if an app doesn't need a server for work, these app can open and work correctly even if it's downloaded from ***** repository.Also, i doesn't know how you can verify the app purchase itself, I think these are more difficult who verify

This is a question for App Review to decide upon. One observation - if the current version of the app is for the iPhone, there is an App Review requirement that all iPhone apps run on the iPad (in iPhone mode). In fact most reviews are performed on an iPad and for this reason, the issue with failing to operate properly on an iPad is detected. So in the upgrade which you propose - features that were available in the earleir version now require in app purchase, but the iPad version runs in a native manner on the iPad.Unless the App Reviewer is knowledgeable with the app, they are likely not to be aware that a previously free function is now an in app purchase item. I have no idea as to if an specific App Review guideline might apply. However, I think the issue will be discovered by your existing users, specifically those who may be using the current iPhone version on an iPad and are expecting the free feature to just work. On the other hand, the iPad app is native.rich kubota - rkubota@apple.comdevelop

I read those. But either am I blind or that scenario isn't listed there. But nonetheless I filed a bug. So hopefully it gets fixed befor the public release.

Thank you for confirming!I can also confirm the issue persists in beta 2. I'm surpised this bug isn't listed in the Known Issues for watchOS beta 2.

There are two iPodTime stretchers on iOS and from the complexity / performance vs. quality trade off view of the world you can think of these two as simple and not so simple.kAudioUnitSubType_AUiPodTime (iOS Only) - Simple - Time domain algorithm. This AU can only perform time stretching. Lowest quality, very fast, suitable for speech. When selecting the kAudioQueueTimePitchAlgorithm_LowQualityZeroLatency Audio Queue algorithm or AVAudioTimePitchAlgorithmLowQualityZeroLatency audioTimePitchAlgorithm, this is the AU being used.kAudioUnitSubType_AUiPodTimeOther (iOS & OS X) - Not So Simple - Time domain algorithm. Much better quality and more flexible than AUiPodTime, fast, suitable for speech but can also be applied to music. When selecting the kAudioQueueTimePitchAlgorithm_TimeDomain Audio Queue algorithm or AVAudioTimePitchAlgorithmTimeDomain audioTimePitchAlgorithm, this is the AU being used.The other Time AU available on iOS and OS X is kAudioUnitSubType_NewTimePitch. NewTimePitch is

Thanks you, this worked! This is the correct answer, except the path you mean is:~/Library/Developer/Xcode/watchOS DeviceSupport/Watch1,2 2.0 (13S5255d)/Symbols(You're missing the leading / and the Watch1,2 before the OS version.)To clarify for others, step 4. is performed on the Choose Destination phase of the pkg installer. Use the above path that you pre-created.

Same problem for me as well. This started with El Cap R1 and didn't fix itself with R2 release yesterday. I can receive icloud emails but the outgoing server is blank and can't be selected. The + - edits in the SMTP lists are greyed out so I can't add it back.I also lost passwords for Gmail and other IMAP accounts but they worked fine on reentry. Exchange account not affected at all.Stuck with no outgoing icloud mail at the moment.

I ran into this problem and found a workaround: if you add a completely new account to Mail, as part of the setup process it asks you to configure an Outgoing Mail Server for the new account. If you go through this process it will take the information you provide in this setup and add it to the list of configured SMTP Servers. So, I basically went through the process of adding a dummy account and then when I got to the end, I seemed to run up against another bug that prevented me from completing configuration of the new account. But when I cancelled and opened up the previous account, the newly added SMTP Server was available from the list of available servers.

I had the same problem and tried two things: 1) I made sure all of my items were synched with icloud and then turned off synching on my phone, deleted the calendar from my phone, re-enabled synching and let everything repopulate on my phone. 2) Performed the Reset Sync Data on my Apple Watch App on my phoneWithin a few minutes everything had synched back to my phone and is now showing up on my watch. I hope this helps, as I'm not sure exactly which activity solved my problem.Good Luck!

Also, 1. Will the watch be able to discover and connect to networks around itself?2. Will the known Wifi networks be listed on the Watch as it is in Settings -> Wi-Fi on the phone?

Thanks for the clearification.If credit or debit cards is specified, will that filter the list of cards that is presented to the user accordingly?