Partially Working as of 06/08/2019

[Omfgcheese]

Hello All,

Been following this and nishnet2002's code for quite sometime and it appears that it does not seem to work completely as of ~1-2 weeks ago. Happy to Paypal someone to get this going again.

Best,

Omfgcheese

[kton]

As posted in the SD thread w/r/t the "there are still some unclipped coupons - something probably broke this script" message:

You can ignore it if everything on your screen shows as clipped, but re-running the script still says there's a few unclipped coupons.

That message typically pops up when there's a store-specific coupon available for your account that can't be clipped due to your current store selection - change your store to some others in your area and you'll eventually find it.

And in the chance that you're not able to find it at any of the stores you regularly shop at - then there's really no point in spending time trying to find that coupon; mine was a free item with purchase-of-$xx-or-more using delivery or drive-up-and-go.

PRs welcomed for anyone willing to go down the rabbit hole; I don't shop at enough Safeway locations for this to bother me :-)

[ADobin]

I did some basic research on this and looks to be solvable; if I have time I'll get to a pull request for it. The error code in the response for those coupons includes the storeId that it's valid for. You can resubmit the same request passing a different storeId and it will clip the coupon successfully. How much value this actually gives you is debatable since for my use case I usually only shop at the store that I have set as my default so getting a random coupon for some other store doesn't really get me any value.

[kton]

Thanks for looking into it.

I'm not sure where you're seeing the storeId in the error response.

Whenever an invalid coupon is clipped, the server responds with a HTTP 200 (ideally this should be HTTP 400, but whatever).

The JSON response I get back is in the following format:

{
  "items": [
    {
      "clipType": "C",
      "itemId": "NNNNNNNNNN",
      "itemType": "SC",
      "status": 0,
      "checked": false,
      "errorCd": "ABCDENNNNF",
      "errorMsg": "Invalid or Unsupported Item for Clipping."
    },
    {
      "clipType": "L",
      "itemId": "NNNNNNNNNN",
      "itemType": "SC",
      "status": 0,
      "checked": false,
      "errorCd": "ABCDENNNNF",
      "errorMsg": "Invalid or Unsupported Item for Clipping."
    }
  ]
}

Poking around through the store list, I can eventually find the appropriate storeID, which is only 3 (completely different) digits.

window.AB.userInfo.j4u.storeId = "NNN"

Agree that solving this minor issue may not provide much value.
It may be beneficial to leave it as-is so that folks can check out neighboring stores for those one-off offers.

[ADobin]

I just had this happen again to me and maybe I'm just getting lucky because of my store numbers. My outgoing request was to https://www.safeway.com/abs/pub/web/j4u/api/offers/clip?storeId=2734 but the response I got back was

{
  "items": [
    {
      "clipType": "C",
      "itemId": "1608732527",
      "itemType": "SC",
      "status": 0,
      "checked": false,
      "errorCd": "EMJOC2063E",
      "errorMsg": "Invalid or Unsupported Item for Clipping."
    },
    {
      "clipType": "L",
      "itemId": "1608732527",
      "itemType": "SC",
      "status": 0,
      "checked": false,
      "errorCd": "EMJOC2063E",
      "errorMsg": "Invalid or Unsupported Item for Clipping."
    }
  ]
}

Using the 2063 as the store id for that item https://www.safeway.com/abs/pub/web/j4u/api/offers/clip?storeId=2063 let me then successfully clip that coupon.

[kton]

I received the same EMJOC2063E error code when testing across multiple accounts associated with different geographical locations (CA, WA).

It appears that omitting the storeId (or using a bogus one like 9999) in the request URI will also yield a "status": 1 response.
The site and app both seem to reflect this "successful" clip on a clean session (clear application data/logout and re-login) like it does when you clip with a valid storeId.

I recall that this (submitting a clip request without a storeId) is how coupons were clipped prior to the website refresh.
https://github.com/kton/Safeway-Just-for-u/blob/safeway-nimbus/src.js#L12

The API behavior is questionable and I don't feel like investigating whether or not this works in practice with an actual purchase.
It'll be difficult for the average user to reclip a coupon with a valid storeId if a coupon does not initially apply at checkout.

For anyone that's up to the challenge, simply replace:
var request = new Request(window.AB.couponClipPath + "?storeId\x3d" + window.AB.userInfo.j4u.storeId, {

with:
var request = new Request(window.AB.couponClipPath, {

.. and let us know how it goes at checkout.

[jwgooru]

Hi Kelvin I replaced your new code:-----------var request = new Request(window.AB.couponClipPath + "?storeId\x3d" + window.AB.userInfo.j4u.storeId, { with:var request = new Request(window.AB.couponClipPath, {

…

---------------- Used old vs. new bookmark to compare:- The new code works smoothly without seeing "unclipped coupons" verbiage, shows "all coupons are clipped" at popup.- The old code does show "unclipped coupons" popup, I clicks on blue OK button, takes a refresh, works ok as well.  I am using the new code now, and will pass on to all my friends who are using your script daily to update.  Thanks a lot!!!June On Saturday, October 26, 2019, 07:49:13 PM PDT, Kelvin <notifications@github.com> wrote: I received the same EMJOC2063E error code when testing across multiple accounts associated with different geographical locations (CA, WA). It appears that omitting the storeId (or using a bogus one like 9999) in the request URI will also yield a "status": 1 response. The site and app both seem to reflect this "successful" clip on a clean session (clear application data/logout and re-login) like it does when you clip with a valid storeId. I recall that this (submitting a clip request without a storeId) is how coupons were clipped prior to the website refresh. https://github.com/kton/Safeway-Just-for-u/blob/safeway-nimbus/src.js#L12 The API behavior is questionable and I don't feel like investigating whether or not this works in practice with an actual purchase. It'll be difficult for the average user to reclip a coupon with a valid storeId if a coupon does not initially apply at checkout. For anyone that's up to the challenge, simply replace: var request = new Request(window.AB.couponClipPath + "?storeId\x3d" + window.AB.userInfo.j4u.storeId, { with: var request = new Request(window.AB.couponClipPath, { .. and let us know how it goes at checkout. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[rgalverson]

Drat, it looks like Safeway broke the clipper again. I have 111 coupons that won't clip...

[q00u]

Drat, it looks like Safeway broke the clipper again. I have 111 coupons that won't clip...

Same. Came here to see if I was the only one.

[kton]

made a small change and tested that it works for me

previously: script would attempt to clip all coupons, even in surrounding stores
this resulted in 'oh no - some coupons could not be clipped' leading to some confusion

now: script scope limited to the store that you have selected

untested: online ordering

[jwgooru]

Kelvin, you are the best. Many thanks! On Sunday, March 1, 2020, 06:21:31 PM PST, Kelvin <notifications@github.com> wrote: made a small change and tested that it works for me previously: script would attempt to clip all coupons, even in surrounding stores this resulted in 'oh no - some coupons could not be clipped' leading to some confusion now: script scope limited to the store that you have selected untested: online ordering — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.