If you're using Azad commercially (for drop shipping, or helping manage procurement etc.) you are not alone. A few "commercial" features are requested frequently. There's a reasonably straightforward path to delivering some of them. Significant investment in time might be required for the others.
To make progress, two challenges need to be addressed:
- Prioritisation. You can help by filling out this (<1 minute) anonymous voting form (new and improved - you no longer have to be me to access the form: sorry!)
- Motivation. I share and work on this extension for free, but need donations to the linked hospice charity to be more proportional to the value commercial users are receiving. At the moment, the vast majority of donations appear to be from private/family users, not businesses, and the total amount donated is a tiny fraction of both the value of my donated time, and the value business are receiving.
- Wait for a clear signal from commercial users on which feature proposals are most popular.
- Build a roadmap and set charity donation targets for the milestones.
- Donation targets reached => work happens on milestones in my free time.
- You (probably) get features you want.
- We all feel virtuous.
Health warning: I am but a simple developer - Amazon has the power to break this extension any time it likes by changing their websites.
https://chrome.google.com/webstore/detail/amazon-order-history-repo/mgkilgclilajckgnedgjgnfdokkgnibi
If you've not read through this document (and indicated that you've done so in the help request), your help ticket may be closed without further comment.
Clear amazon cookies: open chrome://settings/siteData and type amazon in the search box, then delete them all. This will log you out. Then log back in and try again.
Maybe a new version of the extension has broken how the cache data is interpreted, or Amazon has changed their website breaking compatibility between the cached data and the live site (the cached data contains amazon generated urls).
If the extension is working, stop it by pressing the stop button. Then click the "Clear Cache" button and resume normal use.
Parts of Amazon's websites appear to have defences against denial of service or site scraping attacks. If the extension needs to make a lot of requests (because you've got lots of orders or you choose many years, then it can log you out. This often happens only for types of orders or types of order related pages (payments, details) etc, leaving the other types of pages functional. The extension detects this and opens up a new sign-in page so you can log back in. Once you've done this, you can restart the year fetch - it should avoid re-fetching stuff it's already put in the cache.
Symptoms: pending task count sticks at a non-zero number for many seconds. I don't understand why this happens, but the workaround that has always worked for me is to remove all amazon cookies (this will log you out) and then everything works again. If you look in the extension logs (see below), a clue that this is appropriate is entries in the log that complain about too many redirections.
The extension needs to be updated by developers to learn the new layout. Please check to see that no-one else has filed a ticket for the same problem. If they have, join in the fun on that ticket rather than making your own "me-too" ticket. At some point you're going to need to work with us by providing debug data and testing experimental versions of the extension. I don't have direct access to your orders (or likely you country's version of Amazon), so if you're not willing to help, please don't waste everybody's time with a ticket - your issue will not get fixed.
See Amazon changed their site above.
Your first step should be to go to chrome://extensions and click Update. After you do this, close and reopen the Amazon page and rerun the report to see if that helped.
Next, open chrome://settings/siteData and type amazon in the search box, then delete them all. This will log you out. This is particularly useful for fixing problems where it looks like the extension got stuck/bored - sometimes Amazon starts giving the extension the run-around with infinite redirect links. Deleting cookies and logging back in seems to work. You don't need to delete non-amazon cookies.
Please go to https://github.com/philipmulcahy/azad/issues to see issues which have already been reported.
If you believe that you have the same issue, please add a comment. If the issue you have seems new, please create a new issue and describe what you see and what you expect to see.
Either way, please include the Amazon address, such as https://www.amazon.com/gp/your-account/order-history
This serves two purposes:
- You'll be notified of updates.
- The project owner will be able to contact you for more information, if needed.
Before you send log files, debug info, or screenshots, please be aware that postings on GitHub are NOT private. If you have log files, debug info, or screenshts to send but don't want them to be public, please ask how to send.
- Log files are usually free of personal info.
- Screenshots can be edited with a image editor to overwrite anything you don't want public, such as name, address, product description, or last 4 of the card.
- Debug info contains info you'd probably want kept private (though we've not seen any credit card info), so don't post it on GitHub.
- On the screen showing the report, press Ctrl+Shift+I (Cmd+Shift+I on MacOs) to open Chrome Developer Tools
- The Console log might appear at the bottom of the screen, but if it doesn't press "Console" (near to top of the tools pane)
- Once the console is open, do your thing with the extension. If you command a scrape and only then open the console, you'll probably only get the last few hundred lines of log. I think this is to save memory.
- RIGHT-click on the log pane and select "Save as..."
- Save the file as desired.
- You can only do this when you see the results table.
- RIGHT-click on the order ID link (in the order id column) for the row with the issue.
- Select "save order debug info".
- The debug info should automatically save to your downloads folder.
- DO NOT attach this file to a github ticket - although it doesn't contain passwords or full credit card numbers, it is likely to contain your name and address and some details of stuff you've ordered. Instead, send it to [email protected] with the subject line including the ticket link. I (Philip) do not monitor this email address so you should also post on the ticket to say you've emailed a json file.
- Q: Who gets to see my data?
- A: The developer of the extension and possibly a small group of collaborators. The data is kept in a private repo whose maximum number of developers is limited to 10. Currently only one collaborator has access.
- Q: Why do you keep the data?
- A: To ensure that the fixes we prepare using your data stay fixed (known as a regression test).
This may be necessary if you are sent a link to a zip file (probably something like https://mulcahyfamily.org/azad/azad_12345678.zip)
- Download the zip file
- Unzip it to a folder
- Open chrome://extensions/
- Set "Developer mode" (slider in top right hand corner)
- Disable any existing installed Amazon Order History Reporter extension - you don't want two of them fighting (slider in bottom right of the extension's tile).
- Click "Load unpacked" (top left)
- Navigate to the azad folder you unzipped in step (2)
- Open an Amazon tab and start testing.
- Remember to uninstall or disable the test version once you've finished playing. It will not automatically update with fixes, unlike the chrome web store version.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent