Vers 8.1 w/Mobility 3.0.2 and Custom Modules in AA - Deployment "fails"

[RJLedger]

Added in a good custom module (via RMB add custom Module) and it all came in fine.

Had built this w/external gist ok and manually deployed/tested ok.

Mobility deployment is NOT deploying the "custom parts".

Anyone else seeing this.. or are we just lacking the right info??

[RJLedger]

OK.. got past not "seeing" the deployed (custom) pieces...

Now after I've changed the index.aspx, etc... and flushed all cache ... even tried another system.. cannot "see" the mods.. humm..

[RJLedger]

Tweaked things a little.. (massive cache flush, etc).. and now it's working.

[greensweater]

I'm trying to deploy argos-sample on an 8.1 cloud server and I'm not seeing the behavior in the argos-sample docs:

4. If you are deploying using AA 8.0+ then all you need to do now is within AA right click on CustomModules in the SLXMobile portal and choose Add Custom Module. Then browse to the module-info.json file and hit okay. AA will handle building, minifying, editing the index files and enabling you to select/deselect modules as needed. Make sure to save and re-deploy after any changes.

AA is not "editing the index files" as stated above. So apparently you definitely need to edit the index files yourself.

Also the caching is very aggressive in the browser. You have to clear it for every change, or use index-nocache.html for developing.

Chrome: go to chrome://appcache-internals/ and click "Remove" under the Manifest entry marked for slxmobile.

Firefox: under Options > Advanced tab > Network tab, click "Clear now" next to the line "your application cache is currently using..."

IE: Tools > Internet Options > Settings (in Browsing history section) > Caches and databases tab 

[RJLedger]

I already had it all working w/no issues - thanks.. Including having AA automatically insert the appropriate custom changes in the index file(s) ;-)

Not only will it do ONE custom module.. I've got it doing about 20 ..

However, We still do all actual development/debugging OUTSIDE of AA since AA is basically useless when it comes to handling javascript.  All our dev work is done in Webstorm. Just using AA as a way for final deployment for customers.