Found out a solution for that as Mr.Rambo said its a time caliculating bug. We have to decide between two annoying things. The irritating screen popup or clear our call list and change the date back a few days. It worked for me on my 6s and iPhone X Check if it works on your devices.
Found out a solution for that as Mr.Rambo said its a time caliculating bug. We have to decide between two annoying things. The irritating screen popup or clear our call list and change the date back a few days. It worked for me on my 6s and iPhone X Check if it works on your devices.
I have found aswell that you don’t need to clear your call list. Just setting the date back a few days was sufficient for my device.
Found out a solution for that as Mr.Rambo said its a time caliculating bug. We have to decide between two annoying things. The irritating screen popup or clear our call list and change the date back a few days. It worked for me on my 6s and iPhone X Check if it works on your devices.
I did this but went one step further and restored the time back to the correct date. Worked. Big has gone away.
This bug has been "bugging" me for the last two days. I updated Tuesday, so I wasn't sure why i was getting this notification days after updating. I noted a similar pop up in the last beta, but once you dismissed it, it didn't come back.
Rather than tying these notifications to the expiry date of the previous beta, Apple should check your iOS version and badge the app just like with normal iOS updates. I guess they really wanted to push everyone's testing to the latest beta.
"It looks like this method in Springboard does some date/time calculations"
That might explain the bug I reported with Siri.
If you have a contact that includes their birthdate (month, date, and year) and you ask Siri how old they'll be on their next birthday, it replies with an age that is 1 year off.
Are people here in the beta program that have nothing to do with actually testing it?
It’s “Beta”. The “B” might as well stand for “Bugs”. Why is this even being reported on? Slow day?
Are you actually in software development?? I’ve been doing it for decades, and the field-update mechanism of a product is something you want to really nail early. It’s the one thing that, if it becomes inoperable, leads to a complete support meltdown. The fact that it’s buggy 12 days before go-live and for a product where Apple actively encourages non-developers to try it *IS* a little scary, and definitely newsworthy.
Found out a solution for that as Mr.Rambo said its a time caliculating bug. We have to decide between two annoying things. The irritating screen popup or clear our call list and change the date back a few days. It worked for me on my 6s and iPhone X Check if it works on your devices.
I did this but went one step further and restored the time back to the correct date. Worked. Big has gone away.
I tried this and it didn’t work. Strangely, the backlighting turned itself off when I changed the date back. I locked and unlocked, didn’t see the notification anymore (and the backlighting came back). Then set the time back to now and the notifications came back with every unlock or Notification Center view. Bummer of a bug!
Got this on the previous 2 public betas but on this latest one it's MUCH more frequent - like every time I unlock the phone. It's a beta build tho and if that's the worst I have to deal with then well done Apple! I've had much worse experience with expensive supposedly "final build" software at my work.
This is what beta releases are for. However, if the bug is as described and tied to an expiration date it seems like it's an odd bit of logic. These types of update services are typically either Push based where the server pushes a message to the client device to inform the device of a change, or Pull based where the client device periodically checks with the server to see if any changes are needed. Engaging the user through a popup notification should always be conditional either way, i.e., only done if a change is necessary. Strange.
This Beta has got to be the buggiest one yet. I am getting this pop up as well and although it doesn’t do any harm, it is still quite worrisome that Apple would even release a Beta with this type of issue. It’s as if they are messing with us. I do not expect another update until the final version of 12, so get used to this, people.
Comments
It’s “Beta”. The “B” might as well stand for “Bugs”. Why is this even being reported on? Slow day?
link to comment: https://forums.appleinsider.com/discussion/comment/3085911/#Comment_3085911
Rather than tying these notifications to the expiry date of the previous beta, Apple should check your iOS version and badge the app just like with normal iOS updates. I guess they really wanted to push everyone's testing to the latest beta.