Another title of the issue can be EAP-TLS network authentication profile becomes untrusted randomly after a break of 1-2 days - manual intervention required for re-establishing connectionIf any wifi connection is established after WPA2 authentication, then the password remains in memory of the iPhone and the network remains a known network without any limit on the number of days. However, if the network connectivity is made using EAP-TLS mode and identity is taken from a profile downloaded and installed on the iPhone, then it is seen that the network does not remain a known network after 1-2 days. In this scenario the user has to intervene to select the same network again manually and click "Trust" button for the profile to authenticate and connect to the network. This requirement of having to click for trusting the profile to connect to the same network at the same location is happening randomly and intermittently after 1-2 days. This is even though the the network connection has been made once earlier using the same profile and the connection is required to be made using the same profile and with the same wifi network. This problem is not faced by Android based phones while connecting to the same network and at the same location- thus this problem is not a network issue. Further, this problem is faced by all users at the same location on different iPhone devices- thus this problem is not an issue with a specific iPhone device. This problem is also faced by any iPhone at all similar networks which use EAP-TLS mode with a profile for authentication-thus this problem is not due to any particular wifi network. This problem is also not faced by iPhone while connecting to any wifi network through WPA2 or using any other authentication mode which does not use a profile- thus this problem appears to be due to iOS configuration of keeping a network as a known network in its memory. It does not occur if the connection has been established once on a day. However this problem recurs randomly and intermittently after a disconnect from wifi network connection with an interim gap of 1-2 days.Steps to Reproduce:1. Open Settings2. Open WiFi3. Select a network out of the available ones4. Click Mode> EAP-TLS5. Move back. Click Identity6. Select the installed profile for authentication7. Move back. Click Join.8. It connects.9. Disconnect from the wifi network10. Switch of WiFi for that day either from iPhone or from the WiFi router11. Switch on WiFi router and the iPhone WiFi the next day.12. The connection to the earlier connected wifi network does not happen without manual intervention of Trusting the profile.Expected Results: The WiFi network connection through EAP-TLS mode which requires profile for authentication should remain a known network even after any number of days of break in network connectivity. Accordingly, if the connection has been established atleast once, it should happen automatically when the same network is detected by the iPhone after any number of days of break.Actual Results: The WiFi network with which a connection has been established once, does not remain a known network after a break in network connectivity for 1-2 days. The user has to intervene manually and click Trust on the Profile which is used for authentication to the network almost every time after a break of 1-2 days of network connectivity.Version: iOS 10.1.1 (build 14b150)

What are the specific network ports that should be open on my internet connection broadband to enable the following: ) Pairing of HomePod with iPhone. ) Downloading and updating of watchOS. I have already checked the following links, but they do not provide the details for the above mentioned port requirements: https://support.apple.com/en-us/HT202068 https://support.apple.com/en-us/HT202944 The ports mentioned for Airplay and Homekit etc in these links are already open, yet I am unable to perform the activities mentioned. iPhone is already updating on the network, but watchOS is not updating on same network. Changing network completes both activities. Please help.

Content type key header added by iOS mail app contains ‘@yahoo.com’, - causing mail to get rejected by some IMAP servers. Issue is occurring on all iOS versions including 14.6, 14.7 betas, and iOS 15.0 betas. On the iPhone, I am unable to forward a mail containing attachments received from a web browser based @yahoo.com or @icloud.com mail account. When the iPhone native mail app forwards a mail received from @yahoo.com or @icloud.com mail account using a web browser like Safari, it adds the following header content to the mail:  Header added by iPhone mail app: --Apple-Mail-91EF9D82-D8B5-41DD-A98A-69489ED47254 Content-Type: image/jpeg; name=image0.jpeg; x-apple-part-url="xxxx-yyyy-zzzz@yahoo.com" Content-Disposition: inline; filename=image0.jpeg Content-Transfer-Encoding: base64 Content-Id: xxxx-yyyy-zzzz[AT]yahoo.com The header added by iPhone mail app is rejected by some third party IMAP mail accounts who reject the message from iOS mail app. The error message generated at IMAP mail servers is as follows: Mail send failure log: Action: failed Status: 5.0.0 (permanent failure) Remote-MTA: dns; [xxx.xxx.xxx.xxx] Diagnostic-Code: smtp; 5.3.0 - Other mail system problem 550-'5.7.1 Attachment type not allowed. File "image0.jpeg;  x-apple-part-url="xxxxxxx-yyyyy[AT]yahoo.com" has the unacceptable extension "com"' (delivery attempts: 0) Is the error of mail rejection on account of iPhone incorrectly adding the header, or is the mail server behaving incorrectly by wrongly rejecting the mail?

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.

Two of the iOS bugs affecting my work, have been reported multiple times on Feedback Assistant over last many months, yet they are not fixed yet. Anyone else too facing them? They are: Sending SMS Text message (Green Bubbles) on a dual sim iPhone FAILS upon using “Respond with Text” with an incoming phone call from a caller to whom SMS has not been sent earlier after a reset of iPhone settings.  Scheduled fetch and notifications not done by native iOS Mail App for favourite mailboxes on non Push supporting mail accounts (IMAP/ Yahoo/ Gmail etc accounts)- favourite mailboxes updating only upon manual fetch.

'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?

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?

unable to send mail containing pdf attachments from IMAP mail account using SMTP on iOS device mail app- same mail gets sent on other than iOS devices. Sending email on SMTP from native iOS Mail client is failing with attachments. Issue is occurring on iOS 14.4, 14.4.2. The Mail sending does not fail with mails without attachments. The failure happens on all networks when there are pdf attachments in the mail.  The same mail with pdf attachments gets sent successfully from other than iOS device like a MacBook or Windows computer mail client (like native Apple Mail or Microsoft Outlook) using same IMAP account (which is failing in iOS) on all types of networks. No such error occurs when connecting through Gmail or outlook.com accounts. The error occurs only with IMAP type accounts and only on iOS device.  The Console on macOS shows the following line of error: SMTP Delivery for messageID (null) failed with error MFError Domain=MFMessageErrorDomain Code=Generic(1030)

Ever since updating to build iOS 10.1.1 (build 14b150) from iOS 10.1, battery life has drastically reduced. Previously with iOS 10.1, the battery lasted for around two days with one 100% charge. However, since updating to iOS 10.1.1 (build 14b150), battery is not lasting even one complete day. Sometimes, the battery drops around 10% in just 15minutes. This happening with no change in the software configuration or other settings.The battery life percentage displayed on the screen sometimes flickers and changes its value suddenly- upwards or downwards.