When I am trying to build my sencha touch 2 app for production using the command "sencha app build production", I am getting an error as shown in below image. I am not getting the reason for the error.
Looks like you are using a reserved Javascript keyword or perhaps left a debugger; somewhere in your code.
Related
This is the error I am facing at the time of building the ios for my expo app.
Here is the code for Image Picker I used
This is working great in my simulator expo app as well as in iphone expo as well but giving this error while building using eas build -p=ios
I try doing different things and after trying many things I get to know it's because of outdated verions I updated everything in my package.json with the help of expo doctor I see compatible and install them and it's fixed.
I was trying execute myapp to android but an error occurred.
To clarify what happened, first time I install nodejs and Android Studio.
Later I used the following commands:
npx react-native init 'app'
cd app
npx react-native run-android
Its my fisrt time messing with react native, I was following this page:
https://learn.microsoft.com/pt-br/windows/dev-environment/javascript/react-native-for-android
And the error is:
The error
I want coding in real time for android app.
How can I fix this?
Looks like the terminal output gives you several steps to do/check.
Make sure you have properly set up your android environment. Use this link to do so. You can use Expo-Cli or React-Native-Cli.
SDK location not found. This could be an off-shoot error of not properly doing step 1. However, to cover all of your bases, ensure you have properly set up your Android Emulator. This doc is a great walkthrough.
Once your Android studio and AVD Manager is properly set up, and your development environment is properly set, you should have no issues!
Please let me know if doing the above to steps did or did not solve your errors.
If you follow the steps, https://reactnative.dev/docs/environment-setup and https://developer.android.com/studio/run/emulator there will be no problem.
As a React Native fan on Windows 10, I'd like to mention just few points you need to check.
First, please check following user variables in Environment Variables ( You can see it from System Properties).
adb="C:\Users{username}\AppData\Local\Android\Sdk\platform-tools"
ANDROID_HOME="C:\Users{username}\AppData\Local\Android\Sdk"
JAVA_HOME="C:\Program Files\OpenJDK\openjdk-11.0.15_10"
Path: check if contains {ANDROID_HOME}\platform-tools
Eg:"C:\Users{username}\AppData\Local\Android\Sdk\platform-tools"
Second, if you are using Android Sdk emulator, please make sure that it configured correctly in emulator list in Android Studio.
For an instance, I created a android emulator using android sdk-29 and you can check the followings.
Third, I recommend you, deploy first app on emulator in Android Studio.
Because we need to download gradle zip file and others, it's essential to run your first android app in Android Studio.
When you confirmed your first android app(Deploy empty project app is also okay), you can run your React Native App by Expo-cli or react-native-cli.
I've been using sencha Cmd since its release and after every update I face some new issues.
Last one, using sencha Cmd Sencha Cmd v5.0.2.270 and sencha touch 2.4, I cant even produce a valid package build.
actual build using cmd 5 and sencha touch 2.4 (not even good build folder):
https://dl.dropboxusercontent.com/u/35041662/build2.4/bad.PNG
previous build (the one I need):
https://dl.dropboxusercontent.com/u/35041662/build2.4/good.PNG
After the "sencha app build package", I deploy it into a "local server" (something phonegap alike) and when I try to run the project, it keeps me asking to reload the app due to an change in one of the app's javascript and never achieve to run.
alert Message:
"Requested: '[...]/js/appverse.js seems to have been changed. Attempt to refresh the application?"
Btw the production an package build generate a cache.appcache file and the app keeps me asking for reload, in previous version of cmd those files didn't exist.
Thank you in advance
It's no longer supported as from 5.0.2.270.
I had the same problem and the only way to solve was, to install the npm cordova within Sencha Touch (sencha cordova init).
After that I can now use the app.cordova.www folder.
I am struggling for building a Sencha application so need ideas how to build it quickly. I will give you some background about the issue.
I am working on a hybrid app which is built on sencha framework . The app is ready for deployment. This package will be used to upload it in phonegap to create ipk/apk files.
Problem : I got stuck in building process of application. As per sencha touch documentation, we can do it by running following this command:
Sencha app build package
However getting a compile error stating ruby dependency. I Installed ruby however the error still persists.
I suppose I am having conflicts with the Sencha tools versions. I tried with Sencha CMD 2.0.0 and Sencha touch 2.0.1.1 versions but nothing happened. Then I upgraded both of them to Sencha CMD 5.0 and Sencha touch 2.3.1 but same results.
Questions:
1. Do we require anything else except Sencha CMD and Sencha touch?
2. How to upgrade application to latest versions?
Idk if my answer will take you in the right direction or not but when I first started and wanted to make changes with stuff involving ruby I had to use the CMD with ruby that gets installed when you install ruby. Its pretty much the same everything but supports ruby. I couldnt do a lot of things in the regular CMD.
please specify more detail i am not getting but if you want to upgrade your app use first go to your application path and type "sencha app upgrade"
I am working on a sencha touch 2.1.0. I have created production build using sencha cmd 3.0.The production build is successful but While running the application (production build) , I am getting following error
Error evaluating http://xx.xx.xx.xxx/DH/DH_Prod/production/app.js with message: TypeError: Object [object Object] has no method 'getController'.
I am working with 2 controllers in my application and both are working fine until I created the productionBuild.
I got the actual solution as below.
There were places where I was directly accessing the controller such as this.MYapp.getController('MyController') and not as this.getApplication().getController('MyController') which was causing the issue during the production build but not in development version.