Does the Google Play Console have a way to roll out an app update in stages?
In the App Store Connect (iOS) there is this type of option, which gradually releases the app to all users for seven days, so that if a bug is detected in the launch by a number of customers, it is easier to correct it before it reaches all app users.
I've noticed the Android emulator from Android Studio at MacOS 12.6 changes time to some random one. For example it's 16:11 now but emulator shows time 15:16. If I set time to correct one manually it's changed back to wrong one after some time without emulator being suspended or rebooted.
I tried to turn off all automatic time and zone detection but it didn't help too. Also I'm not sure why wouldn't emulator synchronise time if automatic sync is on.
It seems to be a long lasting bug in emulator. The issue https://issuetracker.google.com/issues/257097404 is created in Google's bug tracker
Issue: The build hangs with "iPhone is busy: making Apple Watch ready for development"
Further facts:
iOS 14.8
iPhone 8
watchOS 7.6.2
Xcode 13
Apple Watch Series 3 + Cellular (42mm)
Does anyone know a solution for that issue?
Many of the developers have the same issue:
https://developer.apple.com/forums/thread/691452
I have been struggling with this for some time now. If you don't need the Apple Watch, instead of turning it off completely, you can also turn on airplane mode if configured correctly.
On your watch, go to Settings App → Airplane Mode. Make sure that both WIFI and Bluetooth switches are turned off!
When the bluetooth switch is turned on, a connection will still be established even if your watch is in airplane mode AND bluetooth is turned off on the phone from Control Center. It took me some time to figure this out...
Update: The Bluetooth setting seems to turn itself on again after some time! No idea why... 🤷🏼♂️ Keep that in mind and check the setting again if flight mode does not fix your issue.
Using Flutter?
When running flutter doctor, it will give you a clear hint, that your watch is causing the issue.
When trying to build your app e.g. from Android Studio, you might instead find these messages in your log:
The requested device could not be found because no available devices matched the request.
Available destinations for the "dev" scheme:
[list of devices]
Could not build the precompiled application for the device.
Building a deployable iOS app requires a selected Development Team with a Provisioning Profile. Please ensure that a Development Team is selected by:
[instructions how to set the development team]
Ineligible destinations for the "dev" scheme:
[list of devices]
I put these messages here for people googling them. If you have an Apple Watch, then run flutter doctor to check if this is the root cause.
This is what works for me:
Turn off the Bluetooth from settings in your iPhone from Settings -> Bluetooth (Don't turn it off from the control center)
Quit Xcode
Launch it again
Build and Run
The solution is:
Waiting for 5-20 mins
Let your iPhone and Apple Watch on
I think all answers are overlooked, you don't need 5-20 mins if you let it finish the preparing process, it'll take just a few minutes, 5 mins top..
But regarding fixing this with an upgrade, that's not the case, and I would love to see it fixed, or offered with an option to exclude watch from the dev purpose unless really needed.
I facing this issue too. This is because the latest xcode only support until iOS 15.2 sdk, but my phone's iOS version is 15.3. Thus, xcode is downloading the iOS 15.3 sdk from your phone that's why takes time (I knew the message is not saying that)
However, I do some testing and it works for me.
Get the iOS 15.3 sdk (is 10BG!!!) from my friend xcode's Devices Support iOS folder /Users/XXX/Library/Developer/Xcode/iOS DeviceSupport and paste it to yours one.
Downloading the iphone OS device support file from https://github.com/filsv/iPhoneOSDeviceSupport/blob/0e8ef7bc51b982304ed3258454f88ae2d5615ac7/15.3.zip unzip it and paste it in /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport
Restart Xcode.
Build success without waiting.
Origin From: https://developer.apple.com/forums/thread/691452?answerId=704424022#704424022
The Apple Watch configuration takes around 5 minutes. It's way better to postpone everything and let it run for 5 minutes then the other workarounds - such as disconnecting your watch, turning on/off your iphone, etc
In my case:
If my Apple Watch is turned on - then from Xcode I'm still able build and run the app just fine.
But when I'm using Flutter - it fails.
flutter devices shows my iphone as "Busy".
As soon as I turn off the Apple Watch, and then disconnect and reconnect the iPhone USB cable - all is good.
Since it's one of the earliest Apple Watch modules, the latest WatchOS that I can install is v6.3, although the latest available is WatchOS v8.x.
I suppose this issue doesn't occur with the latest WatchOS.
(I'm using iOS v15.2)
This still happens from time to time. The solution that has worked for me every time is to reboot the phone
Make sure you're running a version of Xcode that supports the SDK versions of your iOS/watchOS device. If you've recently updated either OS versions, you may need a matching Xcode update for this to work properly.
The real solution is:
If you don't need the apple watch you can just power off the Apple Watch and unplug/plug the iPhone. That's a quick fix. No need to unpair the watch no need to wait 5 - 20 mins
According to this post, this issue is fixed with an upgrade to iOS 15.0.2 / watchOS 8.0.1: https://developer.apple.com/forums/thread/691452
In my app, I timed the duration it takes to navigate to one particular screen.
In Android simulator about 700 ms and about the same or faster on the device.
In IOS simulator about the same but on the device over 4000ms - 5x slower!
On the device in debug mode but on the release version also super slow.
I'm trying on iPhone 6.
What could cause such a slowdown?
Do I need to optimize the build - config file somewhere.
Maybe the iPhone6 has a processor that needs to be built for - arm???
I am working on API LEVEL 17 supporting back upto 8. I have some network task to perform that I am doing from seperate AsyncTask class. Now the problem is that whenever I try to launch the application on emulator first time will be fine, but from 2nd onwards my emulator response is slower and gets more slower on successive launch. after 4-5 launch It installs the app but never starts the activity. Then I have to restart the emulator and it also need a startup after 4-5 launch.
I have seen in logcat skipped ### screens!!! UI thread might be doing to much work right from the starting of emulator.
Can anyone tell me what could be going wrong? Thanks in advance!!!
Regards,
Sourabh
Your system configuration is less for android api 17 version your app work properly in api level 8 to 10, so you can set api level 8 to 10.
Surely process of Emulator starting is slow, as lots of threads and process starts-off when emulator starts. Still for better start timing you can download Intel atom emulator from Android SDK Manager, its also available for android api version 17, Also there is option of choosing Snapshot for emulator, which takes less time for start-off.