Showing posts with label Bug. Show all posts

A major FaceTime bug that is publicly broadcasting on the social media right now, which allows you connect to someone and hear their audio without the person even accepting the call, and raising up a huge privacy concern because you can force a FaceTime call with someone and listen to what they are saying, maybe even without being noticed by them.

To take advantage of the bug, all you have to do is add your phone number to your already started FaceTime call, then you will found that you have begun a group FaceTime call including yourself and the audio of the person you originally called, though they haven't accepted the call, which obviously creates a major FaceTime problem.

There appears to be no way to avoid this bug other than completely disable FaceTime on iOS and macOS, and Apple has said the issue will be fixed in a software update later in the week, in a statement to Axios: "We’re aware of this issue and we have identified a fix that will be released in a software update later this week."

For now, you can either delete the FaceTime app or just disable the feature completely under the Settings - FaceTime.

Update: Apple disabled Group FaceTime feature for now

It's the time of the year that when Apple launched new iPhones, there is always bugs popup, this year is no exception.  For example, the connection signal gate, beautygate, chargegate, and other issues, now a new gate has surfaced, we call it "speakergate".

As the name implies, it is a bug related to the speakers: an unknown number of iPhone XS and iPhone XS Max users report that the speakers on their devices are not working properly. Users from Reddit, as well as from TwitterApple Support Communities says that Earpiece speakers of their iPhone XS and iPhone XS Max will stop working while playing music.

Users are very pleasing that the iPhone XS use the Earpiece speaker and the bottom speaker to create a stereo effect. However, after a few days using the iPhone XS Max, the Earpiece speaker stops working. Restarting the device seems to solve this problem, but it won't take long for the problem to repeat itself.

Oddly enough, when you call someone the issue doesn't exist, that is, although it needs to wait for a while, the problem can be fixed by software update. We contacted Apple to ask the company's view on the matter. However, there has not been a response from Apple.

Image Via

Some users said that their iPhone XS and XS Max could not be charged properly after the screen turns off. When you want to charge, you must turn on the screen and restart plug in the Lightning cable. This could be an issue related to the software rather than the hardware, as many users reported this also happens on older devices.

Unbox Therapy tested eight iPhone XS and found that most iPhones were unable to charge with the screen is off. Under normal circumstances, following the iPhone is plugged in, the screen will wake up and start normal charging like what it suppose to do. In the case, the iPhone stops responding entirely at when Lignthing cable plugged in and is screen off.

Despite some users suspected the issue related to USB Restricted Mode, with the goal that is designed to prevent people from unlocking iOS devices communicating with USB accessories through the Lightning connector that one hour has passed since the owner unlocked it. However, Unbox Therapy believes this is not related to the USB feature.

We should expect Apple to release an update that hopefully fixes the issue. In the meantime, there is no workaround for this particular problem. Apple hasn't yet responded on the matter, and if they do, we'll update the post as soon as possible.

Apple released iOS 12 couple weeks ago, though it promised to focus on software quality and privacy issues, however, a bug in the iOS 12 allows anyone to passcode bypass then accesses contacts and photos that works even on iPhone XS, according to a YouTube video posted by EverythingApplePro Channel.

Bypass and access contacts is not simple anymore, as the YouTuber says you will need to invoke Siri, ask it to enable VoiceOver, call the phone number, when the 'slide to answer' interface shown up, click on the message icon twice, then tap on Contact twice, press on the '+' button, then send a message from other device to this device, the display all the sudden change into white screen, tap on and swipe the display many times, enter numbers, tap on a contact, then click on the "i" icon, and you can see the contact info.

Unlike most iPhone passcode bypasses, the process is far complicated, but appears to work, provided the attacker has physical access to a device that has Siri enabled. It works on every iOS 12 devices such as iPhone 5S all the way to iPhone XS, however, it's unclear if it works for non-iOS 12 devices.

Currently, it's likely Apple will fix the bug rather sooner than later, in a form of iOS 12.0.1 or other. Well, it does look like Apple still needs some work on iOS 12, although this seems pretty tricky to do it. We will update if Apple responds the matter.

For users who have already installed the latest beta version of iOS 12, they have encountered an annoying bug. Every time you unlock your iPhone, an update prompt popup will appear, it says that "A new iOS update is now available. Please update from the iOS 12 beta."

However, the problem is that users who have been updated to the latest version and there are no updates that need to be installed. It begins on August 27th, but in the past few days, the frequency of pop-ups has increased significantly. In the worst case, each time you unlock it, each time it appears.

Developer Guilherme Rambo believes that the error in the latest beta version caused the beta to think that the expiration date is approaching, so it constantly reminds you to update. So based on that info, we have got a workaround: go to Settings -> General -> Date & Time, switch off Set Automatically, and change the time to Fri Aug 24.

It's expected Apple will release a new beta rather sooner than later to fix the annoying bug. Stay turn!

There is a serious bug discovered in macOS High Sierra that someone with physical access to a macOS machine can access and change personal files on the system without needing any admin credentials. The bug, found by developer Lemi Ergin, lets anyone log into an admin account using the username "root" with no password. 

This security vulnerability works when attempting to access an administrator's account on an unlocked Mac, and it also provides access at the login screen of a locked Mac. Which means Users who haven’t disabled guest user account access or changed their root passwords (likely most) are currently open to this vulnerability.

The first step to fixed the bug is disabling guest account access. This can make it more difficult for an attacker to jump in and change system settings. After you disabled guest access, the next step is to changing the system’s root password. This can put a stop to the vulnerability altogether. Here’s how!
  1. Go to System Preferences, then click Users & Groups (or Accounts).
  2. Click the lock icon, then enter an administrator name and password.
  3. Then Click Login Options.
  4. Click Join (or Edit).
  5. Click Open Directory Utility.
  6. Click the lock icon in the Directory Utility window, then enter an administrator name and password
  7. Choose Edit > Enable Root User, then enter the password that you want to use for the root user.

It appears that this bug is present in the current version of macOS High Sierra, 10.13.1, and the macOS 10.13.2 beta that is in testing at the moment. It's not clear how such a significant bug got past Apple, but it's likely this is something that the company will immediately address.


“We are working on a software update to address this issue. In the meantime, setting a root password prevents unauthorized access to your Mac. To enable the Root User and set a password, please follow the instructions here. If a Root User is already enabled, to ensure a blank password is not set, please follow the instructions from the ‘Change the root password’ section.”

Via MacRumors And 9to5Mac, Image Credit MR And 9to5Mac

According to MacRumors, there are at least a few hundred iPhone users have complained about the word "it" autocorrecting to "I.T" on iOS 11 version. Affected users said when they type the word "it" into a text field, the keyboard to shows "I.T" as a QuickType suggestion. After tapped the space key, the word "it" automatically changes to "I.T."

A growing number of iPhone users have voiced their frustrations about the issue on some of discussion platforms on the web shortly after iOS 11 was released in late September. Majority users claim that the apparent autocorrect bug persists even after rebooting the device or perform other basic troubleshooting.

A temporary workaround is to tap Settings > General > Keyboard > Text Replacement and enter "it" as both the phrase and shortcut, but still some users insist this solution does not solve the problem. Another method is to toggle off auto-correction and/or predictive suggestions completely in Settings > General > Keyboard.

Recently, Apple fixed a similar bug which caused the letter "i" to autocorrect to "A[?]" with iOS 11.1.1 update. It's worth to notes that the company doesn't appear to be fix the "it" to "I.T" issue in iOS 11.1.1 and later. We are expecting that a future software update will be required to address the problem. As of now, the Cupertino firm did not respond to multiple requests for comment about this particular issue.

A bug in the built-in Calculator app in iOS 11 is getting some major attention this week, despite the fact that it's been around since iOS 11 was in beta testing. According to a long thread on Reddit (via Loop Insight), the issue appears to stem from the fact that the app blocks all input during the animation for the button fades. 

For example, type 1+2+3 and then the equals sign into the Calculator app quickly, due to animation lag introduced when adding two or more numbers together, your result is more likely to be 24 than 6. We'd say this is an iOS problem rather than an isolated Calculator issue. Although iOS 11 betas did allow for taps to register before a UI animation finished playing, that behavior changed in the official release of iOS 11.

Any iOS developers will see what is wrong here: the bug is that the animation that lights up the button is blocking touch events until the animation completes. This is the default behavior for animations, but to make an app feel responsive it's best to find a way around that (it can be a one line fix, but sometimes it is complicated).

Some users have experienced similar issues when using older versions of iOS, but the animation lag is noticeable enough in iOS 11 to make the Calculator nearly unusable when attempting to make rapid calculations. However, iOS users who need a reliable alternative can use third-party apps like Calcbot and PCalc.

Apple seems to be aware of the issue, as The Loop points out, Apple employee Chris Espinoza says more than 70 people have filed a Radar report on the bug, alerting Apple to the problem. We can confirm that this is not fixed in the most recent beta of iOS 11.1, with it received so much attention, users could potentially see a Calculator fix in the next iOS 11 updates.

Via MacRumors And iDB, Image Credit iDownloadBlog
Powered by Blogger.