Expected Behavior
StoreUsageCharge request class (which extends FormRequest) should allow access to request input parameters using standard Laravel request accessor methods.
Inside the request class, input values such as price, description, signature, or any other parameter should be retrievable reliably.
Current Behavior
In Osiset\ShopifyApp\Http\Requests\StoreUsageCharge, the $this->request object is always empty.
Debug output from the attached screenshot clearly shows:
$this->request->all() → []
$this->request->has('redirect') → false
$this->request->get('price') → null
$this->request->get('description') → null
$this->request->get('signature') → null
However, the same values are present in the request and can be accessed correctly when using FormRequest’s own accessors:
$this->all() → ['price' => '1', 'description' => 'Five e-mails', 'signature' => 'hmac-value', ...]
$this->input('price') → "1"
$this->input('description') → "Five e-mails"
$this->input('signature') → "hmac-value"
Root Cause
Since the class extends FormRequest, input access should not rely on $this->request, but instead use:
$this->get()
$this->input()
$this->all()
$this->has()
$this->query()
Failure Information
The bug prevents request parameters from being read when $this->request is used inside the request class, including inside withValidator() where HMAC verification is performed.
Context
- Package Version: v25.1
- Laravel Version: v12
- PHP Version: v8.4
Failure Logs
No exception is thrown, but debugging confirms the request object is not populated:
$this->request → []
$this->all() → contains valid input
Attachment

Expected Behavior
StoreUsageChargerequest class (which extendsFormRequest) should allow access to request input parameters using standard Laravel request accessor methods.Inside the request class, input values such as
price,description,signature, or any other parameter should be retrievable reliably.Current Behavior
In
Osiset\ShopifyApp\Http\Requests\StoreUsageCharge, the$this->requestobject is always empty.Debug output from the attached screenshot clearly shows:
However, the same values are present in the request and can be accessed correctly when using
FormRequest’s own accessors:Root Cause
Since the class extends
FormRequest, input access should not rely on$this->request, but instead use:Failure Information
The bug prevents request parameters from being read when
$this->requestis used inside the request class, including insidewithValidator()where HMAC verification is performed.Context
Failure Logs
No exception is thrown, but debugging confirms the request object is not populated:
Attachment