"Listing error - valid postal code" on mobile

sowth
Community Member
Tried to list two auctions with the eBay mobile app tonight, both come up with the "Listing error - valid postal code" at the final step, very frustrating. I have other auctions currently running and have been using app for months with no probs previously. App is fully up to date. Anybody else experiencing this?
Message 1 of 6
Latest reply
5 REPLIES 5

Re: "Listing error - valid postal code" on mobile

sowth
Community Member
Error says "Trading. Application. 100000737."
Message 2 of 6
Latest reply

Re: "Listing error - valid postal code" on mobile

sowth
Community Member
Swapped from iPhone to iPad and the error goes away.
Message 3 of 6
Latest reply

Re: "Listing error - valid postal code" on mobile

The trouble with trying to diagnose where the problem lies is that despite your apparent prior success with it, the app is known to be notoriously buggy, yet by the same token, it is also true that eBay has been experiencing some really peculiar intermittent postcode-related issues as well, and the fact that the app worked OK on your iPad could indicate that your problem was actually with eBay rather than the app.

 

It's difficult to prove either way, but as soon as the app worked on your iPad, I'd have been inclined to immediately attempt listing again on the iPhone. If it once again failed to function properly, I'd be inclined to blame the app, but if it worked OK this time, I think I'd be more inclined to suspect that eBay was again experiencing one of its intermittent glitches. It's nowhere near definitive proof, but the results may help you to determine whether the problem was with ebay, or the app itself.

Message 4 of 6
Latest reply

Re: "Listing error - valid postal code" on mobile

sowth
Community Member
Thanks for your feedback. I'll be listing a couple more items tonight so I'll try on the iPhone first to see if happens again...
Message 5 of 6
Latest reply

Re: "Listing error - valid postal code" on mobile

I started having this problem today as well. Never had this problem before. I updated the app yesterday for ios8, pretty sure that update is what broke it...
Message 6 of 6
Latest reply