Friday, September 30, 2016

Re: GWT google crawler error undefined.cache.js

Hi Thomas,

Thanks for the fast reply :), it's been a while we didn't exchange !

I tried set-property-fallback, but this means I have to migrate to a newer gwt version (2.7 or 2.8). The issue is that the compiler for those two versions stops unexpectedly without any error message (it only writes "linking succeeded"). In addition, when it succeeds in compilation, I can't run the app in standard mode : the compiler of the super-dev-mode triggers even if I launch the app in standard mode (and I need to see what happens with the production js)

With all these issues and because the bug is critical to fix as fast as possible, I decided to downgrade back to 2.6.1 where I don't have these unexpected compiling failure without errors ... :-/

Actually I need to find a solution for the 2.6.1 version (where set-property-fallback doesn't apply), I will have more time to understand what happens with the new GWT compilers when this bug will be workarounded...

On Friday, September 30, 2016 at 7:05:06 PM UTC+1, Thomas Broyer wrote:
Have you tried set-property-fallback?

You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment