iOS 16.4 requires Tailwind app V2.42 or higher

Follow

Comments

43 comments

  • Sonny Kang

    Thank you!!

    1
    Comment actions Permalink
  • Scott Riesebosch

    My pleasure Sonny!

    0
    Comment actions Permalink
  • Francesco

    Yeah, been on 16.4 public beta a while. For me, auto close works while open does not. Let’s hope there’s a fix soon🤞🏼

    1
    Comment actions Permalink
  • Blue9711

    I wish every app developer would notify and keep their customer base informed . It saves everyone so much time wasted on troubleshooting something that’s avoidable! Thanks Scott and I’m a long time user of tailwind !

    2
    Comment actions Permalink
  • Scott Riesebosch

    Thank you for the kind words. Much appreciated.

    0
    Comment actions Permalink
  • Hope Barrett

    And if/once a stable beta is released that fixes this, please let us know. I run beta too and for while my auto open has not been working while everything else in Tailwind has been fine. This is probably the reason why.

    1
    Comment actions Permalink
  • Scott Riesebosch

    Yes Hope absolutely. We will send another notification through the app to iPhone users, and I will be keeping this article updated with any new information as it becomes available.

    1
    Comment actions Permalink
  • Ralph A. Somers

    Thank you Scott, this is one of the things I love about Tailwind. You really care about your customers, thanks for looking out. Much appreciated.

    2
    Comment actions Permalink
  • Dave Lehmer

    I have been running the beta and it hasn’t been working, but didn’t really make that connection until now. Hopefully they’ll get it fixed quickly. I have the release candidate right now and it’s still broken.

    0
    Comment actions Permalink
  • Francesco

    Anecdotally with no data, the other day my door opened automatically for the one and only time since I got 16.4b1, but my wife had arrived home 15 seconds before me and her door opened normally. My TVS has never been associated with her phone, so I’m wondering if somehow mine communicated through hers? Or her TVS through my phone? I just figured mine had started magically working again. But the next day it didn’t, so here we are.

    0
    Comment actions Permalink
  • Scott Riesebosch

    Ok I have an update. I have written an update and appended to the top of the article.

    In short - problem should be resolved within days and you'll be able to update to iOS 16.4.

    1
    Comment actions Permalink
  • Francesco

    Fantastic! Great support and follow up as always, thank you and your team, Scott. I continue to sing the praises of my Tailwind system and your company to whomever will listen. 🙂

    1
    Comment actions Permalink
  • Blue9711

    Appreciate the update! Keep up the good work tailwind!

    1
    Comment actions Permalink
  • Scott Riesebosch

    Thank you everyone. Your support is very much appreciated!

    1
    Comment actions Permalink
  • Dave Lehmer

    Apparently Apple is also unaware of these changes, because the shortcuts app is not tracking my location in the background either, but wherever there’s an iOS update, shortcuts usually gets broken for a little while.

    1
    Comment actions Permalink
  • Tom Hoffman

    Dave Lehmer This does not surprise me. In doing Microsoft and Apple support for my organization the people doing the first levels of support rarely have any clue what the product team is baking (or breaking). Even months after fixes are released, they do a piss poor job of documenting the relevant changes in their release notes. 

    Francesco @All I have noticed, at least for me, that keeping the app open while coming/going, especially with the diagnostic tool running, it seems to do a better job of kick starting the auto-open and auto-close routine as a workaround until the new app version is released.

    Thanks Scott Riesebosch for keeping on top of things and implementing the changes! I have signed in and followed this article to help make sure I get updates in case I miss the push notification through the app or don't see it under "Recent Activity" section of the Help area in the app.

    0
    Comment actions Permalink
  • Dave Lehmer

    Tom, believe me, I work in tech support for a mobile app for one of the major automotive companies… were told NOTHING until users start having problems

    1
    Comment actions Permalink
  • Scott Riesebosch

    I have to give thanks to an amazing support guy we have over at Apple. He was a real champion and got us the information we needed to correct this. We still have lots of work to do this weekend. We will do our best to expedite the app update.

    1
    Comment actions Permalink
  • Scott Jarvis

    Scott Riesebosch- looks like 16.4 is official now.  Are we 'safe' to 'upgrade' to 16.4 now that its not a beta anymore? 

    0
    Comment actions Permalink
  • Ralph A. Somers

    Hi Scott, are we?

    0
    Comment actions Permalink
  • Scott Jarvis

    In theory :-)

    0
    Comment actions Permalink
  • Aaron

    Tailwind Smart c.v.239(478) hasn't been updated for two weeks in the App Store. Until a new app version is made available that addresses issues caused by iOS 16.4, I'm not updating anything to 16.4.

    0
    Comment actions Permalink
  • Scott Riesebosch

    If you update to iOS 16.4 before the next Tailwind app update is released, you will definitely break your auto-open feature. We will keep this article updated and we will push a notification through the app once the updated Tailwind app is available. The changes needed are NOT trivial and we are working as fast as we can to implement and test them.

    You will know when the Tailwind app is updated one of the following ways:

    1) You'll see a push notification about it
    2) You'll see an update to this thread and article
    3) The first time you launch the Tailwind app after it has updated on your phone you'll see "What's New" and it will say "made changes necessary for iOS 16.4" or something like that.

    0
    Comment actions Permalink
  • Francesco

    16.5b1 has been released to devs; I’m in the public beta, so I just took 16.4 Final (20E247) last night. I can wait for the updated Tailwind app. I appreciate all the effort that goes on behind the scenes on a *normal* day, so I can imagine the headaches when Apple throws you curveballs high and inside. Thanks for keeping us informed, Scott. We all know it’s worth our patience. 👍🏼

    0
    Comment actions Permalink
  • Scott Riesebosch

    Updated Tailwind app is now live. Contains support for iOS 16.4. We pushed this through quickly. There may be bugs we didn't catch. Will continue testing, but it is now safe to update to iOS 16.4 as long as you make sure you make sure you have V2.40 of the Tailwind app just made available moments ago.

    1
    Comment actions Permalink
  • Aaron

    Thank you!

    0
    Comment actions Permalink
  • Ralph A. Somers

    Thank you Scott, much appreciated.

    0
    Comment actions Permalink
  • Scott Jarvis

    Just did 16.4 and the v2.40 update and everything seems to be working great!  Thanks Scott and team!

    1
    Comment actions Permalink
  • Scott Riesebosch

    Thanks guys. Please let me know if you have any issues. If you do discover an issue, please send a bug report through the Tailwind app. It will really help us pinpoint the bug and fix it for you. Hopefully that won't be necessary!

    1
    Comment actions Permalink
  • Tom Hoffman

    Scott Riesebosch Thanks for the good news! I updated my devices and confirmed everything is now working as expected!

    0
    Comment actions Permalink

Please sign in to leave a comment.