Version 2.0.48.393 Beta release (bad bug for beta users)

Discussion in 'Official V1Driver Discussion Section' started by mswlogo, May 27, 2018.

  1. mswlogo

    mswlogo Premium Member Advanced User Premium Member

    Messages:
    2,854
    Likes Received:
    2,481
    Country:
    United States
    Joined:
    Nov 1, 2014
    Location:
    MA
    Bug - A bug introduced on Version 2.0.48.389 around May 10th for Beta users only is fixed.

    Choice one of the following to clean up your database:

    1) Do nothing, it will correct itself, but you will notice some old formerly locked out areas alerting and creating new pins. They will have to relearn. The bad pins will eventually get demoted.

    2) Restore a backup. A backup from before May 10th would be ideal. But any backup between now and May 10th may reduce the number of bad pins.

    3) Delete all gpsMute and gpsMuteDem that have a Date later than May 10.

    New or Learning pins since May 10th are not effected.
    Only pins that performed a mute that you have driven by since May 10 are affected.

    Sorry for this mistake and I appreciate all the Beta Tester out there taking these risks.
    Especially the keen user @Pho20 that spotted that spotted the problem and sent me a log.

    How other apps without this logging can be maintained is beyond my comprehension.
     
    Pho20 likes this.
  2. Pho20

    Pho20 Premium Member Intermediate User Premium Member

    Messages:
    208
    Likes Received:
    138
    Country:
    United States
    Joined:
    Mar 12, 2017
    Running much better thanks for the quick fix mswlogo

    I spend 5 hours a day with your app if something’s wrong I can usually spot it quickly!!
     
  3. mswlogo

    mswlogo Premium Member Advanced User Premium Member

    Messages:
    2,854
    Likes Received:
    2,481
    Country:
    United States
    Joined:
    Nov 1, 2014
    Location:
    MA
    Thanks for spotting it. Really good catch. Can’t thank you enough. So glad you were on the Beta list.

    I’m jumping around between 4 Android phones and the iPhone. Android didn’t have the bug. So I just didn’t notice it yet.

    I’m sure some other keen users would have caught it sooner or later.
     
    Pho20 likes this.