iOS Mail App not doing Scheduled fetch and notifications for favourite mailboxes on IMAP mail accounts that do not support Push (Yahoo/ Gmail / IMAP accounts)- fetching in such favourite mailboxes only on manual opening. Observed behaviour: iOS Mail app is not performing the scheduled fetch for favourite mailboxes of IMAP accounts (like Gmail, Yahoo and third party IMAP accounts) which do not support Push. The behaviour does not change with any of the frequency of scheduled fetch - 15 minutes, 30 minutes, or hourly. Scheduled fetch does not occur with any of the frequencies on favourite mailboxes. Mails are not fetched on schedule from any of the favourite mailboxes even after a lapse of many hours/ multiple fetch cycles. Notification for any mail in favourite mailboxes is also not being generated with any of the possible options for selected scheduled fetch frequency. The scheduled fetch works only for the Inbox of an IMAP type mail account (not supporting Push) and not for any of its favourite mailboxes of non-Push type. Upon opening the Mail app, the respective favourite mailboxes of non-Push IMAP accounts shows unread count displayed against each. Only the unread count is shown but the actual mail is not fetched. The notifications did not happen for those mails in favourite mailboxes. The notifications occurs for Favourite mailboxes only if its mail account supports Push, or it is manually opened. This erratic behaviour occurs irrespective of whether the iPhone is connected to the charger or not, network connectivity is WiFi or cellular. Expected behaviour: The native iOS Mail app should perform scheduled fetch and notifications on favourite mailboxes for IMAP/ Gmail/ Yahoo mail accounts which do not support Push. The scheduled fetch should should work as per any of the selected frequency out of the available options (hourly/ Every 30 minutes/ Every 15 minutes). Every favourite mailboxes should get fetched in each fetch as per schedule and no such mailbox to be missed and left out from any scheduled fetch. A notification should get generated for every new mail fetched in such favourite mailbox of IMAP account which does not support Push.

iOS 15 beta 8: While iOS native Mail app is not running in the background (by virtue of being killed from app switcher), the scheduled fetch of favourite mailboxes of any IMAP account does not occur. I think that iOS Mail app has the privileges to fetch even without showing in the app switcher. Thus the existing behaviour appears erratic. In this situation however the Inbox of IMAP mail account gets fetched on schedule even if Mail app is not running in the background. When the fetch happens, the corresponding notifications also appear as per configuration. Is the behaviour of iOS Mail app correct in not fetching favourite mailboxes on schedule if the app is not running in the background?

Notify when left behind not working for any device connected to iPhone on ios 15.2 betas.  However it is working of the iPhone is having iOS 15.1 public release. It also did not work on 15.1 betas, but worked on public release.  Does it mean, notify when left behind does not work on any beta, and is activated at the backhand off apple only for public release.

I want to create an automator quick action to enable creation of tar archives using tar command on macOS on any selected file or folder in finder. Do I have to use Shell Script or something else? I am unable to do it. Someone please help. I am unable to run the following script for creating tar files. Getting error message. Tarfile="$1.tar" count=1 cd "${@%/*}" if [ $# -eq 1 ]; then while [ -e "$Tarfile" ] do let count++ Tarfile="$1 $count.tar" done else Tarfile="Archive.tar" while [ -e "$Tarfile" ] do let count++ Tarfile="Archive $count.tar" done fi /usr/bin/tar -chf "$Tarfile" "${@##*/}"

Is it possible to install some specific file on macOS running Ventura, instead of installing the complete Xcode 15 beta to enable syncing iOS 17 beta device with the macOS. I tried checking device support files on Xcode 15 Beta, but it does not have device support files for iOS 17 under Contents > Developer > Platforms > iPhoneOS.platform > DeviceSupport. The latest iOS version folder available there is for iOS 16.4. Surprisingly, iPadOS 17 beta syncs with macOS Ventura without installing Xcode 15 beta.

'Remove Download' button in right click menu for iCloud folder in Finder on macOS does not work if total number of selected files/ folders at the time are more than 10 nos. If more than 10 non of files/ folders are selected at any time, then the 'Remove Download' button disappears from the right click context menu in macOS Finder for iCloud folders. To click and act on the 'Remove Download' button on context menu of Finder upon right click, the total number of files and folders together must not exceed 10 nos. Is this the behaviour expected, or am I missing something and this observed behaviour is a bug of Finder?

Toggle button for SMS forwarding (iOS Settings app > Apps > Messages > SMS Forwarding) missing in iPhone. Instead of Toggle button for SMS forwarding (iOS Settings app > Apps > Messages > SMS Forwarding) in iPhone ,a grayed out text appears if the other Apple device is logged in to iCloud after the primary iPhone. Messages in iCloud are switched On for all devices, and all devices are on latest iOS, iPadOS, macOS. iMessage is also On. The toggle button appears for SMS forwarding (iOS Settings app > Apps > Messages > SMS Forwarding) in iPhone against any device logged in to Apple account in the following conditions: 1.) the iPhone is restored as new and logged on to the iCloud ID, after the other Apple device was logged in to iCloud with same ID. In other words, the iPhone under consideration and its Messages in iCloud are logged on in the last out of all other Apple devices (iPad, macBook, any other iPhone); or 2.) the messages in iCloud is toggled "Off" in the respective other Apple device. Perhaps the above condition (2) is emanating out of the Apple support article https://support.apple.com/en-in/102545, but the condition at (1) definitely does not seem to have any basis. The behaviour at (1) seems a bug.

WhatsApp is automatically suffixing a number to the device name in the list of Linked devices shown in WhatsApp app settings. The suffixed number has no correlation to the actual number of linked devices at that time. For example, a number “2” is suffixed to the device name in list of Linked devices shown in WhatsApp, even though that computer/ device is the only one shown as a linked device. If we try to edit the device name to remove the suffixed digit, it does not move forward.  I think it has something to do with the restoration of chats from cloud, because the suffixing happens subsequent to the restoration of chats from cloud. Whatsapp does not respond to emails about this issue. Anyone else?

iOS 14.7 and earlier: Unable to send SMS text message (not iMessage) without deleting a conversation, if previous messages were iMessage and iMessage is disabled after initiating that conversation/ sending few iMessages. Expected behaviour: If a conversation is initiated with iMessages (blue bubbles) with any contact, and the user wants to continue the same conversation using SMS messages (green) instead of iMessages, the iOS Messages app should permit it. The conversation should continue using SMS even if the earlier messages sent in it were iMessages and not SMS messages (Green bubbles). There should be no need to delete the existing iMessages conversation in order to send an SMS message (green bubbles) to the same contact if iMessage has been disabled subsequent to sending an iMessage. Observed behaviour: If subsequent to initiating a conversation by sending an iMessage, the iMessage is disabled in iOS Settings > Messages > iMessage > [Disabled], and an SMS text message is attempted in the same conversation, the sms sending fails. SMS text message does not get sent. Instead ot generates error “Message Failed to Send” or “Cannot Send Message”.  If a conversation is initiated with iMessages with any contact, then the user is forced to continue that conversation only using iMessages and not by SMS text messages.