[
https://issues.apache.org/jira/browse/CB-6505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978997#comment-13978997
]
Craig Payne commented on CB-6505:
---------------------------------
Just checked... I can run it on the local RoR instance, and a scan a code, get
a report etc. I have to manually override findCordovaPath's output, setting it
to the correct local value ("/dev-assets").
Local/Dev RoR instances normally do not pre-compile or minify (and mine is no
different).
So it does seem to be a problem with pre-compilation.
> Hybrid app - issues with pre-compiled, minified assets not getting loaded
> -------------------------------------------------------------------------
>
> Key: CB-6505
> URL: https://issues.apache.org/jira/browse/CB-6505
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
> Affects Versions: 3.4.0
> Environment: iOS 6.1, Heroku, Ruby-on-Rails 3.2
> Reporter: Craig Payne
>
> I have an existing RoR application, with pre-compiled and minified assets, up
> on Heroku. I created a Cordova app using
> https://github.com/cfjedimaster/Cordova-Examples.git and following the
> instructions I was easily able to generate an app that ran on my iPhone and
> scanned as expected. When I went to move the one page app's functionality
> into the RoR application I started running into issues where the Cordova
> JavaScript was generating bad paths to, especially, cordova-plugins.js.
> Hacking the code, I bypassed the call to findCordovaPath, hardcoding that
> with "/assets/" - which *almost* works. On my 'local' Dev env I can use
> "/dev-assets" (the RoR default) with the non-compiled, non-minified and I see
> no issues with loading the files. But, switching to "/assets", doing the
> pre-compile, and pushing to Heroku continues to fail.
> Either I'm missing something semi-obvious (and possibly buried in the docs),
> or there's a testing hole here. I can't imagine that using pre-compiled and
> minified assets is an uncommon occurrence, even in Hybrid apps.
> NOTE - this is actually on 3.4.1-0.1.0 which isn't apparently a legal version
> in "Affects Versions" yet.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
