Mixing MIT App Inventor 2 and Thunkable or ANY third party AI clone is a
terrible idea. Mixing can result in unpredictable results with a Project that include corruption of the code, unpredictable performance of the App, inability to load the components of one to another and other undesirable effects. These problems will exacerbate as the clones diverge from the basic OpenSource App Inventor code.
Since you use admob, you should NOT use MIT App Inventor. Thunkable has its own unique Map component system similar to what is used in App Inventor. The Map component, in Thunkable uses Google Maps tiles; App Inventor uses OpenStreetMap tiles. A developer can do more 'things' with the AI Map component. Thunkable cannot find AI's Maps because Maps is built-in to AI but not Thunkable; Maps is not an extension. AI does not provide admob and probably never will ( AI is intended primarily as a teaching/educational compiler). The third party clones are commercial endeavors.
If you need ads, use Thunkable or AppyBuilder. If you want Ai's simple but elaborate full featured Map capabilities, use App Inventor. If you use Thunkable, you probably can use its mapping tool to do something similar or you might modify the Static Map Trak solution to work with
Thunkable's mapping component (both use Google Maps). Thunkable can use Polylines in a way App Inventor uses LineString. It should also be possible to use the Static Map Trak solution with Thunkable (without using T;s Map) . I do not know but think AppyBuilder
might use the same Map component used by AI. You could try AB or building Traks with a Static Map or using Thunkable's map component and polylines and let us know what works.
"Use appinventor (and) there is no problem but i do use thunkable only to admob that is no present in appinventor." Glad the Traks solution works in App Inventor.
Regards,
Steve