After IOS 5.36.0 update, Send Offer functionality broken: ERROR - URL incompatible

[suzzyx81]

After updating the IOS eBay app to v5.36.0, the "Send Offer" functionality is broken. Once you want to send an offer to a potential buyer that is watching an item the app responds after several seconds: ERROR - URL incompatible

This was noticed first on an iPhone 7 Plus with IOS 12.2

We tested an iPhone 6 Plus with IOS 12.4 and 5.36.5 version of the eBay app and this functionality worked fine. After forcing upgrade to 5.36.0 the issue started to happen on this second IOS device too.

As there is no rollback option of the app on IOS platform it is very frustrating because no fast fix seems to be available for this issue, no other than reporting the issue and hoping that the development team can catch and solve this issue soon.

Please fix this,  it’s quite frustrating and really reduces the functionality of the app. Thank you

[mobile_feedback]

---

@suzzyx81 wrote:

After updating the IOS eBay app to v5.36.0, the "Send Offer" functionality is broken. Once you want to send an offer to a potential buyer that is watching an item the app responds after several seconds: ERROR - URL incompatible

This was noticed first on an iPhone 7 Plus with IOS 12.2

We tested an iPhone 6 Plus with IOS 12.4 and 5.36.5 version of the eBay app and this functionality worked fine. After forcing upgrade to 5.36.0 the issue started to happen on this second IOS device too.

As there is no rollback option of the app on IOS platform it is very frustrating because no fast fix seems to be available for this issue, no other than reporting the issue and hoping that the development team can catch and solve this issue soon.

Please fix this,  it’s quite frustrating and really reduces the functionality of the app. Thank you

---

Thank you for reporting this and including screen shots. Do you get the same errors when you are connected via wifi?

[suzzyx81]

Yeah, also tested WiFi and 4G. Same issue on both connectivity scenarios.

[suzzyx81]

It seems that the issue is now fixed. Tested on the two affected IOS devices and is fully working.

Thanks for your fast reply!