[Meteor 1.3-beta.12] (Cross-Post-Issue) Error building with raix:push - Package configured via .json config file
See original GitHub issueHello, i’ve posted the following error to the Meteor Issue Tracker already, see link below.
The thing is, I think it’s possible to configure raix:push without the .json - File, which would be a workaround, but I don’t get exactly how to configure the client side. The docs lead to the recommendation to use the configuration of the cordova push package: https://github.com/raix/push/blob/v3.x/docs/ADVANCED.md#note-outdated , but the supplied link https://github.com/phonegap/phonegap-plugin-push#pushnotificationinitoptions doesn’t seem to lead to an explanation of the config anymore.
Maybe somebody can give a hands-on example of how to deal with it?
Or maybe it’s possible to move this to Meteor.settings or upgrade the Push.Configure - call to set the required parameters for phonegap-plugin-push?
This is the error I posted:
Link: https://github.com/meteor/meteor/issues/6411
Text:
I receive this of error since updating from 1.3 Beta 11 to 1.3 Beta 12:
Error: sourcePath not a file: push.config.web.browser.js
at ImportScanner._ensureSourcePath (/tools/isobuild/import-scanner.js:208:13)
at /tools/isobuild/import-scanner.js:101:28
at Array.forEach (native)
at ImportScanner.addInputFiles (/tools/isobuild/import-scanner.js:100:11)
at /tools/isobuild/compiler-plugin.js:709:15
at Array.forEach (native)
at Function.computeJsOutputFilesMap (/tools/isobuild/compiler-plugin.js:689:19)
at ClientTarget._emitResources (/tools/isobuild/bundler.js:749:8)
at /tools/isobuild/bundler.js:516:12
at /tools/utils/buildmessage.js:359:18
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at /tools/utils/buildmessage.js:352:34
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at /tools/utils/buildmessage.js:350:23
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at Object.enterJob (/tools/utils/buildmessage.js:324:26)
at ClientTarget.make (/tools/isobuild/bundler.js:507:18)
at /tools/isobuild/bundler.js:2232:14
at /tools/isobuild/bundler.js:2322:20
at Array.forEach (native)
at Function._.each._.forEach (/Users/spaceman/.meteor/packages/meteor-tool/.1.1.13-beta.12.1p7kgab++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/underscore/underscore.js:79:11)
at /tools/isobuild/bundler.js:2321:7
at /tools/utils/buildmessage.js:271:13
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at /tools/utils/buildmessage.js:264:29
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at /tools/utils/buildmessage.js:262:18
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at /tools/utils/buildmessage.js:253:23
at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
at Object.capture (/tools/utils/buildmessage.js:252:19)
at Object.exports.bundle (/tools/isobuild/bundler.js:2213:31)
at /tools/runners/run-app.js:586:36
at Function.run (/tools/tool-env/profile.js:489:12)
at bundleApp (/tools/runners/run-app.js:576:34)
at AppRunner._runOnce (/tools/runners/run-app.js:629:35)
at AppRunner._fiber (/tools/runners/run-app.js:881:28)
at /tools/runners/run-app.js:406:12
After a lot of humming and hawing, it seems to boil down to this:
raix:push is structured to be configured using a file config.push.json
in the meteor projects’ root directory.
Then there seems to be some kind of build plugin which is supposed to read the file and actually add some additional javascript. The whole thing is registered here: https://github.com/raix/push/blob/f3a5a653dc2d1d7cd1af0b4d6478d23bcbd0644f/plugin/push.configuration.js#L185
…AAAND that’s how far I can isolate the error. Something (a lot I feel?) changed in the build process from 1.3 Beta 11 to 1.3 Beta 12 and this is one issue which probably needs to be patched somewhere.
Reproduction Repo: https://github.com/DanielDornhardt/meteor13Beta12errorBuildingWithRaixPushPackage
- just remove or rename the file config.push.json to see the build error disappear.
Issue Analytics
- State:
- Created 8 years ago
- Comments:12 (5 by maintainers)
Hey, I’d also be excited about having these settings in settings.json. I already have a system setup to manage dev/stage/prod settings via settings.json, and this extra config is extra work.
Agreed that having keys in settings.json would be ideal.