Why I can't build my custom component with Oracle JET? - oracle

I have created a custom component with ojet, but when I have tried to build it, I got an error: "Error: Invalid platform component"
How have i do it:
I have used the Oracle JET version: 5.2.0
I have created a new web application (proba3): "ojet create proba3 --template=navdrawer:web"
I'v got: "Your app is ready! Change to your new app directory 'proba3' and try 'ojet build' and 'ojet serve'"
"cd proba3"
" ojet serve"
The web page shows up in the browser as I expected.
I have created a new component (zizi-table): "ojet create component zizi-table"
I'v got: "Add component zizi-table finished."
I have have tried to build the new component: "ojet build component zizi-table"
I'v got: "Error: Invalid platform component"
What is the problem?
Any suggestions?
Thanks.

Finally I changed version 6.1.0, and this issue has ceased. This version works well.

Related

CodePush 400: {"status":400,"name":"Error","message":"Missing required query parameter \"deployment_key\""}

After rebuilding with React Native 0.70.1/react-native-code-push 7.05 project/Xcode 14/Monterey , npx react-native run-ios launch successfully without any error but the console screen throws error:
[CodePush] An unknown error occurred.
LOG [CodePush] 400: {"status":400,"name":"Error","message":"Missing required query parameter \"deployment_key\""}
Then I create a new app in MS appcenter for IOS and replaced the app secret with the new one just created in AppCenter-Config.plist in Xcode. But the error is the same. Before rebuilding the app, I verify that the latest react native code push 7.0.5 works with the release of React Native 0.70.
The app build in Xcode 14 went successfully. What is missing with the appcenter or app config?
In my case, I got this error because I forgot to set the CodePushDeploymentKey inInfo.plist :)
Now that I have a configuration-specific CODEPUSH_KEY in build settings, and have set the CodePushDeploymentKey to $(CODEPUSH_KEY) in Info.plist, it works!

What causes this webpack code 2 error and how to solve it?

Cannot even build in sidekick after a simple change
I created a new Core/TS project in Sidekick, I built the app and developed some stuff, but later I changed the icon to a nicer one (which requires a new build, no HMR for this type of change obviously), now I cannot build my app (cloud build, because I don't have Android Studio).
I checked the /main/assets/app/ and the icons were successfully changed there and they were existed.
What is happening? How do I fix this big issue? My patience bottle with all these critical errors even after simple changes is getting emptied.
I also tried "removing .cloud and folder directories", and clicking "clean cloud processes", adding "clean" option, etc...
But none worked.
I also updated the webpack.config.js file, with node_modules.bin\update-ns-webpack --configs
The file got successfully updated, but still did not solve the problem and I still cannot build.
Still after many hours cannot cloud build my app in sidekick. I also tried tns platform remove android, tns install, etc, etc... none worked out.
this is the error message:
[00:00:18.521] [WARN] Executing webpack failed with exit code 2.
[00:00:18.681] [ERROR] clean-webpack-plugin: /mnt/storage/builds/_/af8fe992d35e76b54f5523261a83dac973ffc9ed/5.3.4/5.3.1/Spread/platforms/android/app/src/main/assets/app/**/* has been removed.
Executing webpack failed with exit code 2.
'Build failed with error code 2'.
[19-06-10 19:13:56.767] Couldn't enable debugging for EP7333JKFA, Error: Couldn't enable debugging for EP7333JKFA
at Errors.fail (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\common\errors.js:126:28)
at Errors.failWithoutHelp (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\common\errors.js:136:21)
at LiveSyncService.<anonymous> (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:253:30)
at Generator.next (<anonymous>)
at C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:13:71
at new Promise (<anonymous>)
at __awaiter (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:9:12)
at LiveSyncService.enableDebuggingCoreWithoutWaitingCurrentAction (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:250:16)
at LiveSyncService.enableDebuggingCoreWithoutWaitingCurrentAction (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\common\decorators.js:67:47)
at LiveSyncService.<anonymous> (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:290:25)
at Generator.next (<anonymous>)
at fulfilled (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:10:58)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
OUTPUT 2
EDIT:
SOLVED
https://github.com/NativeScript/sidekick-feedback/issues/384#issuecomment-508028462
I know this isn't an answer, but it is happening to me, too. I am running Nativescript 5.4.1. I can build with webpack, but as soon as I try to run with AOT or Uglify, I can't build and the error message isn't very helpful.
Try to remove and add 'nativescript-dev-webpack'-plugin using nativescript-sidekick-GUI, this resolve my issue...

Parse "parse new " not working

I have just downloaded the ParseConsole.exe run it. I already have an app in my account in parse.com. The problem is that when I run the command "parse new" in the ParseConsole and log in the ParseConsole only shows me "1: results" instead os my app to choose. What should I do? Image of the error
I just came across this and just updated to the latest Parse CLI and it resolved my issue.
https://parse.com/docs/ios/guide#command-line-updating

while importing project in Android Studio throws 'Project refresh failed' error

I am a new bee for Android Studio,
while i import any android gradle(e.g. github.com/k9mail/k-9) project in studio,
it shows a bulk of errors:
Error:Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at http://gradle.org/docs/2.2.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
Error: Could not find or load main class Xmx512m
i also changed the "Gradle VM option" under File>>Setting >>Gradle to "Xmx512m -XX:MaxPermSize=512m"
but not worked for me.
Also in the "VM option" under File >> Setting >> Compiler(Gradle-based Android Projects) i changed the VM option to Xmx512m -XX:MaxPermSize=512m, but not worked for me,
Please help me out.
Thanks in advance.

Deployment error: windows.licensing failed to start WSService

I get the following error when I try to deploy a windows store app:
Error : DEP0700 : Registration of the app failed. error 0xC0020017:
windows.licensing failed to start WSService while installing
My developer license is valid. I changed the package name, still the error persists.
This problem occurs with old and completely new projects.
Does anyone have an idea how to solve this?
Registration of app failed error usually occurs when you try to re-deploy an app with the same package ID from visual studio if it is already installed by a different user.
Solution is to change the Package Identity
Open the manifest
Go to the package tab
Modify the identity

Resources