v0.12.9

fixed #1100, fixed csrf token pattern (#1106)

v0.12.8

Update composer.json to work with Laravel v9 (#1081)

v0.12.7: Add `&__d=dis` to MEDIA_JSON_BY_TAG and update JSON response path in …

…getMediasByTag(), getPaginateMediasByTag(), and getCurrentTopMediasByTagName()  (fix #1052) (#1091)

v0.12.6: Add `&__d=dis` to media URL request (#1083)

Without this Instagram returns a 200 response but with an error message: `for (;;);{"__ar":1,"error":1357004,"errorSummary":"Sorry, something went wrong","errorDescription":"Please try closing and re-opening your browser window.","payload":null,"hsrp":{"hblp":{"consistency":{"rev":1005858897}}},"lid":"7121366591489386466"}'`

v0.12.5: Working getAccountInfo again (#1078)

Co-authored-by: Joe <joe@wpj.cz>

v0.12.4: Use stored session when checking logged-in status (#1030)

* Use InstagramException as a base exception class.

* Try to use stored session when checking logged-in status.

Co-authored-by: test <test>

v0.12.3: Make getCacheKey API public. (#1026)

See details in [issue](https://github.com/postaddictme/instagram-php-scraper/issues/1025).

v0.12.2: Allow getMediasByTag to GraphQL or data access (#1020)

Upgrading a project to php 8 I lost the functionality of `getMediasByTag()` only ever getting a empty array. It looks like a PR changed the array key from ['graphql'] to ['data'] yet 'data' doesn't exist on the responses I get, while 'graphql' does.

On the potential that the response might A) differ from time to time or B) somehow be different based on the request origin or something (i.e. I can't prove ['data'] doesn't work for others, while my ['graphql'] doesn't) I propose the following fallback 'reversion' - check for the existence of ['graphql'] then try ['data'] if it's not found.

v0.12.1

New feature and fix (#1024)

* Add method for get info about current authenticated user

* Change getMediaUrl and Media class to new Instagram structure

v0.12.0

search users by following and followers (#979)