verbb / postie

A Craft Commerce shipping calculator plugin.
Other
12 stars 18 forks source link

UPS Oauth #107

Closed thomasdefilippis closed 1 year ago

thomasdefilippis commented 1 year ago

Describe the bug

Not sure whether this is a true bug, but ups just discontinued api access without oauth. So, likely this shipping method will need a rewrite.

We are under a time crunch to get this working for a customer who is launching in a month. Any chance that this feature could be high on the list since ups method seems to be unusable?

Thanks, Thomas Defilippis

Steps to reproduce

Craft CMS version

4

Plugin version

3.03

Multi-site?

no

Additional context

No response

engram-design commented 1 year ago

It's a known issue, yep! Unfortunately, I can't seem to get a new app setup with UPS, and their support has been frustrating to deal with. If you're willing to setup a test app and send through credentials (just for testing, not production), I'd be happy to continue with the refactoring. You're welcome to get in touch via support@verbb.io.

We're also underway with some major rewrites, and we're factoring in this change into that.

thomasdefilippis commented 1 year ago

Great,

thanks for the quick response.

The only problem with sending you credentials after creating an app is I would rather not share access to my account where a credit card is attached. I could try creating an app and see if I run into any issues. What issues were you having with the process?

thanks, Thomas Defilippis

engram-design commented 1 year ago

Yep, not suggesting sharing your UPS account details, just the clientId and clientSecret of the app you'd create. But I do see what you mean that a credit card is attached to that which would be understandably problematic.

It's more on the last step of the process, we get the following error

image

And UPS support have just come back to us multiple times saying "it's fixed", but it doesn't work. I'm wondering if maybe it's our credit card being Australian, as all other details are pretty basic.

Still working on it!

thomasdefilippis commented 1 year ago

Alright, I tried signing up for a new account, and I got the same screen Screenshot 2023-07-27 at 7 57 21 AM

So, I don't think it is the fact that you have Australian credit card. Also, I know it is the UPS (so they like addresses), but they had me fill out around 4-5 address fields before it errored out. The image below pretty much sums up their process: Screenshot 2023-07-27 at 7 52 05 AM

going to submit a ticket to them as well.

thomasdefilippis commented 1 year ago

Any news on this issue. Want to know if I need to go custom on my own for the ups stuff.

engram-design commented 1 year ago

Actively working on it. Have just started the process to gain a shipping account with UPS, and they're finalising setting it up. All going well, I should have some testing details to be able to create an app and test this.

Did you ever get a response back from yourself being unable to create an app?

thomasdefilippis commented 1 year ago

No unfortunately, every-time I try to create business account it fails with the same message. Are they doing a manual process for you?

engram-design commented 1 year ago

Yeah same on my end. Literally had to call and speak with a rep. Probably won’t get any further action until next week

thomasdefilippis commented 1 year ago

Cool, yeah, I think we are all in the same circumstance. Appreciate your work and look forward to the new release. Any estimation on that release. Are we looking at 3 weeks away or 2 months? Just want to figure out if I should start working on manual setup for ups until this is fixed.

engram-design commented 1 year ago

I would estimate a week or two!

engram-design commented 1 year ago

Added in 3.1.0

thomasdefilippis commented 1 year ago

Great,

I just got api access from ups, so I think they figured something out over there on there end. Thanks for the quick release!

thomasdefilippis commented 1 year ago

Hey one last question:

I noticed that the daily pickup rates for ups were removed in the new version of the plugin?

Was that intentional?