JavaScript-micro-message Access JS encountered this problem

Warning:fopen (Access_token.json) [function.fopen]: failed to open stream:permission denied in jssdk.php on line 79

Warning:fwrite () expects parameter 1 to BES resource, boolean given in jssdk.php on line 80

Warning:fclose () expects parameter 1 to BES resource, boolean given in jssdk.php on line 81

Warning:fopen (Jsapi_ticket.json) [function.fopen]: failed to open stream:permission denied in jssdk.php on line 56

Warning:fwrite () expects parameter 1 to BES resource, boolean given in jssdk.php on line 57

Warning:fclose () expects parameter 1 to BES resource, boolean given in jssdk.php on line 58

Reply content:

Warning:fopen (Access_token.json) [function.fopen]: failed to open stream:permission denied in jssdk.php on line 79

Warning:fwrite () expects parameter 1 to BES resource, boolean given in jssdk.php on line 80

Warning:fclose () expects parameter 1 to BES resource, boolean given in jssdk.php on line 81

Warning:fopen (Jsapi_ticket.json) [function.fopen]: failed to open stream:permission denied in jssdk.php on line 56

Warning:fwrite () expects parameter 1 to BES resource, boolean given in jssdk.php on line 57

Warning:fclose () expects parameter 1 to BES resource, boolean given in jssdk.php on line 58

Under what circumstances. If it is a Linux environment, it will open the read and write permissions of Access_token.json and Jsapi_ticket.json.

Don't tell me you're using the SAE. The SAE does not support local write permissions and has to modify the code.
You can store access tokens inside the memcache of the SAE.

If it is a different system, please open the Write permission.

This is the reason for the SAE as a test environment, and today I have just met. The SAE does not have read and write access to the file.
My condolences

