2013-01-21, 09:36
Ok I see. This is totally unrelated to the launcher App. This is simply an XBMC behavior. When you browse your files from the mobile app, the add-on part is in fact a virtual file system populated by the add-on. When first browsing it from the app you won’t see them because the add-on has not yet published them. If you manually access it within XBMC you will kind of “force” the virtual directory to be constructed an it will then reside in memory. From here you will be able to see the add-on folder on the mobile app. This behavior will change as soon as your app will implement the new Frodo’s JSON add-on interface. I my app I used before a workaround (for Eden if you follow me) to have a direct call to the add-on special folder. It seems to force the Virtual directory to be build.
Hope this is clearer.
Hope this is clearer.