Thank you for your response Rob. I think what the community is saying is that there is a systemic issue. Every thread that has been made for this error in the last few months has 5+ users replying of the EXACT same behaviour at the same time. Unfortunately I have wasted enough of my time on this error already, I hope going forward a permanent solution can be found so we can build without this persistent error message as has been the case for the last 2+ years prior to Febuary. (since I have been using Corona SDK)
Simon