If you're asking is it normal for betas to lack full public release-version power/battery management code, yes. If this interferes with use, it may be better if you avoid betas on daily used devices. Good luck.

There are two limits - one is the max size for download over the air, and the other is max size in the store. You're way over the max for OTA, so... 4GB, uncompressed, is the max in the store - see Maximum Build File Sizes - https://help.apple.com/app-store-connect/#/dev611e0a21f There is no way to exceed that limit and still have an app in the store, however, the solution over the years when the asset requirements go higher is still the same...download from a server of your choice post-install. Apple provides hosting, - https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/On_Demand_Resources_Guide/IntrotoHostingODR.html Amazon, DIY on your own servers, etc. See this article if you are looking for ways to reduce your app's payload: https://developer.apple.com/documentation/xcode/reducing_your_app_s_size Good luck.

Check the release notes - I'd wonder if has to do w/the new vend schemes... Create a fresh sample using an applicable template and see if those calls persist. Feel free to file bugs against the beta, being sure to add your report #(s) to your thread for ref., thanks and good luck.

from the iOS 14 b7 release notes: General ......Known Issues ..........Important Updating to iOS & iPadOS 14 beta from previous versions of iOS & iPadOS might take significantly longer than expected. Data loss could occur if the update is interrupted. (59101197) Might help to clear off another several GB, just to be safe, then restart, run no apps at all, and then try, being sure you're using the latest profile, etc. In the end, tho, it might just be a matter of sitting on your hands and letting the process work itself out. If you live along the West Coast, I'd avoid installing until the wind and power outage warnings subside. Good luck.

Thread 0 & 1 are both symptoms of what may be the root cause, keeping in mind that 'mismatched' IDs can also mean multiple methods named the same. Time to do some sleuthing on your end, and if still no joy, you might need to go thru and use unique names, instead of defaults, in all applicable instances. Still no joy, file bugs against the beta(s) and keep checking/seeing if when 14 goes public, the crashes go silent. Good luck.

Did you indicate an age over 18? Are you inside or outside the US? Seems there are ongoing issues when outside the US. Speaking of issues, see: https://developer.apple.com/forums/thread/126314 Otherwise, 'can not enroll' could mean different things, from simply not being able to interact with the backend (use Safari on macOS), to your payment not being accepted, to not receiving emails from Apple (be sure those are not being spam filtered out of your inbox). Finally, it might be a matter of being patient and trying again later. Good luck.

Not sure there is a simple/native max length. Seen the discussion here? https://stackoverflow.com/questions/35589503/set-maximum-characters-to-one-in-a-nstextfield-in-swift Set a count, then keep an eye on that...

Perhaps this 1.5 yr. old thread has some relation, point being small details due to a beta Safari in general can likely trigger such blips, etc. It might support it, but not entirely, depending on... h ttps://github.com/magcius/noclip.website/issues/10 If you filed bugs, be sure to add their numbers to your thread for reference, thanks and good luck.

Does that mean I need to wait for Xcode production version for iOS 14 to submit my update? Yes, that's exactly what it means. Note that devs are obligated to only use release tools/SDKs/OSs (no betas) for the store. It's good you're testing/getting ready for the next iOS, but you will need to wait a bit longer before you and your users can realize the benefit of that effort.

>with the intention of becoming an iOS developer - I have no idea about Swift and the Xcode Since you're that new, I'd suggest to avoid betas of any type until you get your feet under you. If you're used to thin ice, mine fields, and self-support, then by all means, go for it ;) Good luck in any case.

same as the release of iOS 14? Usually they are in general sync, yes, however, keep in mind that Apple has a long standing habit of releasing updates for tools before updating the backend/App Store Connect, so if your end goal is to upload for the store day 1, proceed with caution.

Perhaps those templates are outdated, and new are on the way, maybe by the time 12 hits public release. See this previous thread for discussion on 12 & splitview controllers: https://developer.apple.com/forums/thread/655195 Xcode 12 b6 release notes also mention SVC: https://developer.apple.com/documentation/xcode-release-notes/xcode-12-beta-release-notes/

flag it in some way to force it to stay in memory  The OS decides what/when to purge for it's own needs, meaning even if your app found a way, the risk of being overridden could arbitrarily negate your scheme, I think.

Might not be something we have control over - the backend, routinely brittle, seems to be acting out more than usual right now. I wonder if they're moving the furniture around in prep for an update to Transporter... Be patient, keep trying, don't waste too much energy beating on it, and good luck.

Devs can test against beta OSs, using beta tools, but as OOPer points out, we are not allowed to submit apps to the store that include them. It is good you are trying to be ready, but keep in mind we haven't seen the final version of OS 14 that the public will be using. Keep testing, and when OS 14 is released to the public, and dev tools have been updated as release versions, to match, then you will can build and deliver a properly qualified app that the store can accept and users can enjoy. Good luck.