Hello @rawilk I went through integrating the shipping and Tracking API into my Laravel application. But the tracking API always returns "No tracking information available"
Please Follow the first image in the response of Shipping API & the second one is of tracking API

Laravel UPS Version

latest v

Laravel Version

v8

Bug description

please update this project now access token not working

Steps to reproduce

No response

Relevant log output

No response

When can we expect support for Laravel 9?
Thank you!

Laravel UPS Version

v2.1

Laravel Version

v10.42.0

Bug description

Just recently, we have been getting a "preventsAccessingMissingAttributes" when trying to create a shipment. Our code is basically a lift of the code in the documentation (as that fits our needs).

I can't find the route cause of this error. Based on my understanding, preventsAccessingMissingAttributes() is related to Laravel models and error management for unselected columns in a query. I'm not sure how this applies in this case as the creation of a Shipment doesn't directly interact with a model. My only thought that the Entity class is somehow involved in this error.

In my testing, it's not just the LabelDelivery method that is throwing the error; we experienced the same issue when generating payment information with the PaymentInformation method.

The Laravel 10 may also be the related. We are using laravel-ups in two separate apps, one running Laravel 9.52.16 and another running 10.42.0; at this time we are only experiencing the error in Laravel 10.42

Steps to reproduce

This error is triggered when creating a new Shipment, with a label, and generating a digest (getDigest).

Relevant log output

Call to undefined method Rawilk\\Ups\\Entity\\Shipment\\ShipmentServiceOptions\\LabelDelivery::preventsAccessingMissingAttributes()

Feature Description

We have Information from our customer support staff at UPS that UPS is in the middle of changing over to OAuth 2.0, and XML/SOAP API Formats will no longer be available starting June 3rd 2024. Instead this will be replace with RESTful Version. I know its a year out, but do you have plans/comments already for this?

Is this feature valuable for other users as well and why?

No response

Laravel UPS Version

2.1

Laravel Version

9.5

Bug description

I got this error when calling tracking api

Steps to reproduce

No response

Relevant log output

No response

Hey rawilk! Amazing package you have here, really helpful and the documentation is very understandable. This "issue" is more of a "feature wishlist" if you would like that kind of input :)

On the shipping class there are labels of the packages generated on the process, this "package" returns an encoded image but the documentation doesn't explain how to convert and save that to the database and project. I solved it like this:

 /* Cleaning the code */
 $image = base64_decode($packages->first()->label_image->graphic_image);

 /* Saving code as an image on a folder in the system */
 file_put_contents('img/tracking-labels/order_' . $order->id . '.gif', $image);

 /* Saving the name of the file */
 $order_package->package_label_file = 'order_' . $order->id . '.gif';

Pretty straightforward. Would be great that this package aids on the decoding of the image and just returning the file to save it on a default folder on a single line, like calling a class or something. Just an idea.

Awesome work, thank you.

Laravel UPS Version

v2.0

Laravel Version

v9.19

Bug description

Shipment with multiple packages always returns single package information

Steps to reproduce

No response

Relevant log output

No response

Feature Description

I have notied that bodies of each request sent to UPS API are formed into XML fomat, but looking through latest documentation of UPS API it suggests to send body requests in JSON format. I think this also cause a The request is well formed but the request is not valid (10002) error getting thrown whenever I try to use the wrapper. Would it be possible in the future to add functionality for wrapper to form requests body in JSON format?

Is this feature valuable for other users as well and why?

The UPS API has changed and will be changing. XML format is also getting slowly replaced with JSON format. I believe it's important to implement JSON based requests for the wrapper.

Using shipping
https://randallwilk.dev/docs/laravel-ups/v2/apis/shipping
Am i able to get quotes before i request for shipping? or do i need to implement the rate class?
1 more question, the shipper_number is the same as avvount number in the UPS dashboared right?

Feature Description

Per UPS Developer Kit website:

If you were sent here by a software provider to obtain an access key, please share the below with them as they will need to update their integration to OAuth auth-code grant type in order to continue to enable their services.

By June 2023, UPS will no longer issue new API access keys.

UPS has implemented an OAuth 2.0 security model for all APIs to enhance the overall security for our customers, reduce fraud and provide enhanced API capabilities. OAuth replaces access keys with a client ID and client secret for authentication. New OAuth credentials must be created on the UPS Developer Portal.

Any chance that the new authentication will be implemented in this package?

Is this feature valuable for other users as well and why?

Package is unusable if you don't have old API keys

Feature Description

Please Explain a little About To update Confirg/app.php file

also
use Rawilk\Ups\Entity\Address;
use Rawilk\Ups\Entity\Package;
use Rawilk\Ups\Entity\PackageWeight;
use Rawilk\Ups\Entity\PaymentInformation;
use Rawilk\Ups\Entity\ReferenceNumber;
use Rawilk\Ups\Entity\ShipFrom;
use Rawilk\Ups\Entity\ShipTo;
use Rawilk\Ups\Entity\Shipment as UpsShipment;
use Rawilk\Ups\Facades\Ups;
have Not found errors

Is this feature valuable for other users as well and why?

No response

Laravel UPS Version

2

Laravel Version

10

Bug description

When can we expect support for Laravel 10?
Thank you!

Steps to reproduce

No response

Relevant log output

No response