Widget
Response from developer
Hello Gary. Thank you for your feedback. Widget support in iOS 26 has been added in the most recent update. If there's any additional views or features you would like to see, please reach out to us at www.tireminder.com/contact, or give us a call at (772) 463-6522.
Issue after latest update
1/17 update. Can’t get the rear tow vehicle to reconnect. Even changing vehicle type turning off unit closing and opening and closing the app.
Update 1/24/25
Went to tire minder in Stuart FL they were able to make sure my unit was on the correct firmware even though the unit show otherwise. The issue with the disconnect and reconnect will hopefully be corrected in the next app update. The staff at tire minder HQ were courteous, friendly, and very helpful.
Response from developer
Hello Class A Owner! - Update (01/22/2025): We've just released a fix for the issue you are experiencing. Please update your app to the latest version for the fix. If you have any further issues, please let us know. Thank you. - Original Response: Thank you for your feedback. Please contact our support team at (772) 463-6522 or info@tireminder.com to resolve your issue. Thanks again and we look forward to correcting the issue you're experiencing.
Issue after latest update
1/17 update. Can’t get the rear tow vehicle to reconnect. Even changing vehicle type turning off unit closing and opening and closing the app.
Response from developer
Hello Class A Owner! - Update (01/22/2025): We've just released a fix for the issue you are experiencing. Please update your app to the latest version for the fix. If you have any further issues, please let us know. Thank you. - Original Response: Thank you for your feedback. Please contact our support team at (772) 463-6522 or info@tireminder.com to resolve your issue. Thanks again and we look forward to correcting the issue you're experiencing.
Issue after latest update
Great Solution But Car Play Does Not work
Response from developer
Hello Alpharisk! Thank you for your feedback. The CarPlay issue described should now be fixed. Please let us know if you have any further feedback.





