2017 BMW 330i (F30) [Vehicle Image Function Returns HTTP Error 424] #497
SalmanBurhan
started this conversation in
Fingerprint data contributions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Everyone! Attaching the vehicle footprint for a
Error Using Image Function
I have had an issue with the image function with this vehicle however.
Prior to the deprecation of the old API, all images would load successfully.
Since the shift to the revamped API used in the new myBMW app, the only
carView
that loads isVehicleStatus
aka deprecatedFrontSide
view.The server returns the HTTP Status Code 424: Failed Dependency with a
get_vehicle_image_failure
error explaining that"[the] user does not own VIN."
My first instinct was to un-enroll the vehicle from the app and re-enroll it but unfortunately that did not solve the issue.
GET Request w/ all Appropriate Headers Present.
Returns an HTTP Status Code 424 with a JSON Response Body
Another Strange Note on Vehicle Year
The Vehicle Is Indeed A 2017 Model. It was a custom build and ordered around the first few weeks of release (Late October, Early November 2016). Production completed in Germany in November of 2016. In the myBMW app, it does acknowledge that this is a 2017 model year, but the server has continuously responded with a vehicle year of 2016, presumably based on the production date. This very minor issue has been present for this vehicle using both the deprecated and current API.
--
Thank you for your time and the vehicle fingerprint files are attached below.
state_bmw_0.txt
vehicles_bmw_0.txt
vehicles_mini_0.txt
Beta Was this translation helpful? Give feedback.
All reactions