Do you think that would cause the first error also?

I understand that it is caused by a unicode character, but nothing appears 
in app.yaml or any file names, so I am a bit confused. Could a space from 
Japanese input cause this? Japanese has been used in the project but there 
is not any visible in the app.yaml file. 

Also, would this suddenly start happening even though I have deployed the 
app several times previously. I made no changes to the app.yaml file or 
file names since the last commit. All I did was add one line in an api 
controller and upgrade to 204.0.0 

On Wednesday, June 6, 2018 at 11:51:44 PM UTC+9, Kenworth (Google Cloud 
Platform) wrote:
>
> It looks like there's an unsupported character in your index.yaml file 
> (probably รข if you use latin-1 encoding). Could you remove all non-ascii 
> characters and try again?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/4d73a4c6-9f42-476e-92c3-00a67d9246d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to