I am trying to implement, an AngularJS App, to work with TideSdk. Everything works fine, if I run it over the browser, but however, I am not seeing any element loaded when I package it as a TideSdk application. The template is not even loading.
I don't find any useful as an error in the console.
Has anyone tried it before.?
I'm currently working on a project which is Angular based with TideSDK, and it's working well. All my routes, directives, services, (...), are working. Could you explain a bit more your issue?
Did you enable the webkit console of the app ? (https://github.com/TideSDK/TideSDK/wiki/Enabling-Web-Inspector => for macos)
All the logs are not present in the TideSDK Developper tool.
Related
I've been creating react-native app to share text or images to social platforms.
I've used React-Native-Share library to serve the purpose of my application.
This library is working fine for iOS & Android but when I'm running it on Web.
I'm facing compiling failed error (Syntax Error). It seems like React-Native-Web cannot parse the syntax used by this library.
As far as I researched on it. I think I need to setup webpack.config.js for this to work, but as I've never did this before so not sure how it works and how to set it up.
Please see the attached screenshot
Syntax Error
Thank you in advance :)
I have an app written in preact which I would like to test, but I am unable to get it working on the Tizen tv emulator.
After some research, I found a few instances of people creating apps for Tizen with react but never actually using preact.
Has anyone experience with getting preact apps to work on the Tizen platform?
thanks in advance :)
There's nothing in preact itself that might cause the app to not work on Tizen. In fact it should work much better then a react version. I've not only seen, but have written apps in React for Tizen (even legacy ones). The real reason of the failure might be that the app is not transpiled appropriately for the Tizen platform. You should be targeting at least ES2015. Also be sure to include pollyfills if you are using fancy data structures, like Set for example.
It would help if you could post the error that you receive in Tizen emulator. You can run the app in debug mode and actually see all suspicious output in the console of the detached WebKit devtools that debug mode auto-opens for you.
I'm using react-native facebook login through this library: react-native-fbsdk. Following the installation guide did not completely get it working, but I managed to get it working after modifications on the native side, as instructed in many github issues etc.
Anyways, it was working fine two weeks ago, but now, when I try to login with facebook, the application immediately crashes. It doesn't open any login page or do anything else.
What is weird is that if I open a browser in the emulator, leave it to background, and then try to login, the login goes further (I get to actually login, but when I'm directed back, the application crashes).
From the tombstone files I am able to get following warnings/messages:
Expected native library version number "",actual native library
version number ""
Tens like these:
Could not find generated setter for class
com.facebook.reactnative.androidsdk.FBLoginButtonManager
How could I solve this problem? And why it doesn't work anymore? I didn't change anything in the code. Only thing I can think of is that it loads something from the internet during compiling the application. How could it otherwise fail?
This is answer for how I solved the problem, not that much about why it was behaving like this.
In short:
I got it working again by updating the emulator and android API 6.0 through Android Studio.
<Rant state='begin'>
I have no idea why this worked, nor why did it broke in the first place. As it was working good with the old emulator and API 6.0 earlier.
It seems like the react-native fbsdk is far from stable. Or then it is completely react-native's fault, idk to be honest. But this just makes me want to develop fully native, instead of react-native, which seems unstable from my experience so far.
<Rant state='end'>
I have 2 HTML5 projects.
One runs on http://localhost:8383 when I click on run.
The other runs on file:/// and (correctly) shows a "Cross origin request" error when loading a json file.
Both projects are relatively simple html+css+vanilla javascript projects.
I compared both projects carefully. Specifically, I compared the project properties. "Sources", "JavaScript" and "Run" appear to be identical. Both projects are set to "With Netbeans Connector", "Chrome", but I tested both with the embedded Webkit Browser as well.
Whatever I try, when I click on "Run", one projects starts as http://, as it should, the other insists to start as "file:///".
Does anyone have an idea where I should look?
EDIT:
Things I tried:
Triple-checking Run configuration settings
Restarting Netbeans
Starting one project first, then the other
Testing both projects with Chrome and the embedded Webkit browser
Thanks in advance.
I faced a similar issue and solved it. I created an HTML5 project using an Oracle JET template.
The issue is with the template which is being used while creating the project. Re-created the project by attaching a different template (older version of oracle jet library) and also created another without attaching any template and it works successfully.
It looks like some compatibility issue between netbeans and the attached template!
My solution was to create a new project and copy all source files over.
Now the play button calls the web service.
I'm working on html5/css3 application based on angularjs. And building this into android application using cordova 3.5.0.
Everything works fine until I hide application using 'home' button on the phone and then restore it: after that whole app reloads, and plugins became undefined.
Any ideas why this happening and how to fix it? Maybe I need to clarify something about project structure?
I wanted to try calling plugins using cordova .exec() but this method is undefined as well.
Well, I figured out what's the problem and I feel really stupid right now.
There is an option in dev options: "Don't keep activities", I was testing application on my co-worker's device and this option was turned on(I believe it turned off by default), so it was the root of a problem.