Android Widget for Mach-E [Less Complex]

[Djmc321]

I changed phones recently and the widget isn't displaying data and is crashing the app after adding to my home screen (using Lawnchair launcher as before). The app-side appears to work initially to log in and setup as usual, but once I add the widget the widget just displays N/A for everything then the app the crashes immediately without error when trying to open. After I removed the widget I can open the app ok again. Can't seem to see anything obvious in the logs but happy to help with any defect triage/testing if you're able to help?

Sponsored

 

[kennelh]

I changed phones recently and the widget isn't displaying data and is crashing the app after adding to my home screen (using Lawnchair launcher as before). The app-side appears to work initially to log in and setup as usual, but once I add the widget the widget just displays N/A for everything then the app the crashes immediately without error when trying to open. After I removed the widget I can open the app ok again. Can't seem to see anything obvious in the logs but happy to help with any defect triage/testing if you're able to help?

Create a new bug report issue on GitHub and I'll work with you there.

 

[Aulander]

I have the same issue on Android 12. I have installed version 2022.03.02: the app does not crash anymore and the widget shows correct data.

 

[Aulander]

kennelh, can you explain me this OTA update info? On the Mach-E SYNC display I get no update notifications. Thank you

 

[kennelh]

kennelh, can you explain me this OTA update info? On the Mach-E SYNC display I get no update notifications. Thank you

Check the FAQ on GitHub. I put my best guess there.

 

[babgvant]

This is awesome! Thank you

 

[kennelh]

Version 2022.03.31 just uploaded. The main addition is for handling app updates. There is now an Update activity which will display the changelog contents (so you can see what's new) and give you the option to update, which then downloads the new APK and hands it to the package installer. Updates are checked for every hour.

There's also a bug fix for European VINs; currently the app is only aware of VINs starting with 3FM (North America) and WF0 (Europe). If your VIN starts with something else, let me know.

 

[Mustang-fyren]

There's also a bug fix for European VINs; currently the app is only aware of VINs starting with 3FM (North America) and WF0 (Europe). If your VIN starts with something else, let me know.

Thanks. With this latest update, the app started working again on my mobile, has not worked for a few weeks. My VIN starting with WF0 (Norway).

 

[Arjan]

Great it now works on my Sony Xperia with my GT ! Only thing not working is the OTA info.
Getting "unavailable"

VIN also starts with WF0

 

[Aulander]

Great it now works on Android 12. Thanks!

 

[kennelh]

Great it now works on my Sony Xperia with my GT ! Only thing not working is the OTA info.
Getting "unavailable"

VIN also starts with WF0

Can you see the OTA info from the three-dot menu? If not, then enable logging, let it run a little while, then save the log. Create a new issue on GitHub and I'll look at it.

 

[Arjan]

Can you see the OTA info from the three-dot menu? If not, then enable logging, let it run a little while, then save the log. Create a new issue on GitHub and I'll look at it.

04/01 22:17:09 D OkHttp3: <-- HTTP FAILED: java.net.SocketTimeoutException: Read timed out
04/01 22:17:09 E 934TXS: java.net.SocketTimeoutException in NetworkCalls.getOTAStatus

04/01 22:17:14 D OkHttp3: {"displayOTAStatusReport":"UserAllowed","ccsStatus":{"ccsConnectivity":"On","ccsVehicleData":"On"},"error":null,"fuseResponse":null,"tappsResponse":{"vin":"WF0TK4Sxxxxxxxx","status":200,"vehicleInhibitStatus":null,"lifeCycleModeStatus":{"lifeCycleMode":"NORMAL","oemCorrelationId":"","vehicleDateTime":"2022-02-02T06:56:23.000Z","tappsDateTime":"2022-02-02T06:56:26.482800Z"},"asuActivationSchedule":{"scheduleType":"","dayOfWeekAndTime":null,"activationScheduleDaysOfWeek":[],"activationScheduleTimeOfDay":null,"oemCorrelationId":"","vehicleDateTime":"","tappsDateTime":""},"asuSettingsStatus":{"asuSettingsState":"ON","notificationSettingsState":"ON","oemCorrelationId":"1793","vehicleDateTime":"2022-04-01T16:29:39.000Z","tappsDateTime":"2022-04-01T14:29:40.457556Z"},"version":"2.0.0"},"updatePendingState":null,"otaAlertStatus":null}
04/01 22:17:14 D OkHttp3: <-- END HTTP (840-byte body)
04/01 22:17:14 I 934TXS: OTA status successful.



I guess this is the problem ?
I tried to open a case but the logfile was too long

 

[kennelh]

04/01 22:17:14 D OkHttp3: {"displayOTAStatusReport":"UserAllowed","ccsStatus":{"ccsConnectivity":"On","ccsVehicleData":"On"},"error":null,"fuseResponse":null,"tappsResponse":{"vin":"WF0TK4Sxxxxxxxx","status":200,"vehicleInhibitStatus":null,"lifeCycleModeStatus":{"lifeCycleMode":"NORMAL","oemCorrelationId":"","vehicleDateTime":"2022-02-02T06:56:23.000Z","tappsDateTime":"2022-02-02T06:56:26.482800Z"},"asuActivationSchedule":{"scheduleType":"","dayOfWeekAndTime":null,"activationScheduleDaysOfWeek":[],"activationScheduleTimeOfDay":null,"oemCorrelationId":"","vehicleDateTime":"","tappsDateTime":""},"asuSettingsStatus":{"asuSettingsState":"ON","notificationSettingsState":"ON","oemCorrelationId":"1793","vehicleDateTime":"2022-04-01T16:29:39.000Z","tappsDateTime":"2022-04-01T14:29:40.457556Z"},"version":"2.0.0"},"updatePendingState":null,"otaAlertStatus":null}
04/01 22:17:14 D OkHttp3: <-- END HTTP (840-byte body)
04/01 22:17:14 I 934TXS: OTA status successful.

I guess this is the problem ?

Yes, there's no fuseResponse in the report. That's where all the data would be.

 

[kennelh]

Version 2022.04.06 just uploaded. It's a fix for the update crash. Of course, you can't use update to get it but I provided a link in the change log to save a few steps there.

 

[kennelh]

I found a method in Ford's API to get all vehicles associated with the user's account, which has led to some big organizational changes in the app. Users with only one vehicle won't notice anything major, but users with multiple vehicles will only need a single login to access the status of all vehicles supported by FordPass. This means the app will now define a "profile" as an individual FP login (and I'm assuming somewhere out there, someone has more than one).

If you are using the app with multiple vehicles and would like to help testing the new implementation, send me a DM and as soon as I can I'll send you a link to a beta version (if you're interesting in testing it but only use it with one vehicle, feel free to jump in feet-first also). I'll be creating a Issue on GitHub specifically for feedback on this.

Sponsored