I'm on Windows 7 64bit and I'm following the Getting Started Tutorial. So far I've:
Downloaded TideSDK-1.3.1-beta-win-x86.zip
Extracted the 3 folders it contains (modules, runtime, and sdk) to C:/ProgramData/TideSDK/
Downloaded and installed Imagemagick
Downloaded and installed Wix 3.0
Downloaded and installed TideSDK-Developer-1.4.2-win-x86.msi
Cloned using Git: https://github.com/TideSDK/TideSDK-HelloWorld
Opened TideSDK Developer tool.
Clicked "Import Project" and selected the cloned Git repository, hit OK. (Screenshot)
Clicked "Test & Package" tab, and then clicked "Launch App" button. (Screenshot)
TideSDK Developer tool says "Preparing to package and launch desktop app. One moment..." but it never does do anything beyond that. The tutorial says I should see this, but I don't.
There are no errors anywhere that I can see. What can I do to get this Hello World app working?
I was not able to get TideSDK to work. However I found something that worked even better: node-webkit.
"node-webkit is an app runtime based on Chromium and node.js. You can write native apps in HTML and Javascript with node-webkit. It also lets you to call Node.js modules directly from DOM and enables a new way of writing native applications with all Web technologies."
https://github.com/rogerwang/node-webkit
Related
I'm getting this error when opening VS Code. Does anyone know what it means? I've done some research but didn't get any relevant information :(
I've tried creating a workflow to see if the error disappeared, but it didn't.
It seems that react native is asking for a workspace to start but is it asking that in the first place? Can I disable react native from running when opening VS Code?
The folder opened when the screenshot above was taken was the folder it opens by default, I believe it's the mac "home" personal folder, and I have a folder called "git" inside of it, with all projects.
Given the date of this posting (2023-02-07), you're probably on version 1.10.0 of the extension. This sounds like this bug report in the microsoft/vscode-react-native GitHub repo: [Bug] Extension activating when it shouldn't #1891.
A fix is coming in version 1.10.1.
But it is taking some time and has not been release yet at the time of this writing 2023-01-31:
we're facing some problems in the last release process, recently we're waiting for new publishing PAT access to republish 1.10.1 again, maybe it will publish on marketplace on next week. We have nightly version for extension in marketplace as well, maybe you can use it now.
For now, you can try installing the nightly version.
Also, note from the extension's readme documentation:
Before going any further make sure that you:
have a working React Native environment.
have the emulator utility available in your PATH if you're developing Android applications.
[...]
Got it, this annoying log came from React Native Tools extension. They specify the requirements in the docs:
In my case, I don't have a specific React Native environment or the emulator PATH is not right.
Just updated my Mac to the official release of Ventura, and I cannot launch my application via react-native run-ios.
Expected behavior:
running react-native run-ios will launch an Xcode simulator and a terminal window with Metro running.
Current behavior:
Xcode simulator opens, main terminal says app was built successfully, but an error is thrown instead of the metro terminal opening:
“launchPackager.command” can’t be opened because (null) is not allowed to open documents in Terminal.
The simulator just shows a white screen and can't be interacted with.
What I've tried:
manually opening node_modules/react-native/scripts/launchPackager.command
opens Metro terminal but is not connected to the app
warn No apps connected. Sending "reload" to all React Native apps failed. Make sure your app is running in the simulator or on a phone connected via USB.
info Reloading app...
giving Terminal full disk access (no change)
This happened to me after upgrading to macOS Ventura. I happen to use iTerm as my main terminal, not the built-in Terminal.app so the following fix only applies to that scenario:
Set iTerm as the Default Handler for *.command Files
Open node_modules/react-native/scripts/ in Finder (open node_modules/react-native/scripts/)
Right-Click on launchPackager.command and click Open With then choose Other...
In your Applications directory, select iTerm and click Always Open With
After this, you might need to run npm run ios again from this terminal window. However, from now on, Metro will open in a new iTerm tab instead of trying to open the command in a new Terminal window.
For me, this was the desired behaviour and it removed this warning.
Note In future, any *.command files will now open with iTerm instead of Terminal.
I encountered the same problem as you, I installed another terminal (iTerm2), then randomly found a .command file, and in the display introduction, changed the default opening method to iTerm2enter image description here
I'm having this issue after upgrading my MacOS to Ventura 13.1.
If you don't want to use iTerm as the accepted answer suggest, the workaround I found was to look for the launchPackager.command file inside node-modules/react-native/scripts/ and open this file manually every time you run your app for the first time (specifically when the error pop-up appears). This will open the terminal with metro running already.
I know that manually processes are not the best, but I don't want to use iTerm :)
Using Intel version of apps (Webstorm, Android Studio, other IDE etc...) fixed my problems. I encountered the same issue and thanks to Intel version of Webstorm and Xcode on Rosetta I can able to pod install and other operations.
Note: I'm using Intel version of Android Studio, WebStorm. Also Xcode uses Rosetta 2. No problem detected and everything works perfect. I can able to develop React-Native & Native Android & iOS and Flutter apps without problem. Before that I was using Silicon version of WebStorm and almost no function worked.
Config: MacBook Air, macOS Ventura 13.2 on Apple M1 processor.
For Most of the case you just have to delete node_modules and install modules again (npm i). This happens when project was copied from old mac which had node_modules folder created by the old user, or if the system thinks so
This happened to me after i configured my terminal for the look and feel - but with iterm2, oh my zsh, and powerlevel10k
First off let me be clear. I have several iOS devices. On the devices that have 7.0.6 I have no issues. When I updated one of the devices to 7.1 I'm having an issue. Let me explain.
On the iOS device that has 7.1 I navigate to the workbench URL and then I go to Manage applications and select install. I then get this message "Cannot install applications because the certificate for >ip address< is not vald. This process works on devices that have 7.0.6. I'm assuming there are issues with the new iOS update.
Now I did some searching and I found something that said there's an issue when trying to download an app from a HTTP site, so I changed a Web Reports setting (found in Eclipse Preferences -> Test -> Performance Test Reports -> Web Reports) to "Security is required to access reports". Thus it changed the port number to "8443". I then navigate back to the workbench URL using the https : // ip:port and try to install the app again. This time it just says Cannot open.
Any ideas on this?
Here is a workaround to be able to test with iOS 7.1
1) Get the zip of instrumented Application from developer or other who can run rtwBuildXcode.sh on a Mac and who has the source code for Application. [RmotXXXXXXXX.zip file]
2) Use RTWec "Add Application to list..." button and brows to the zip to "import" it into RTWec.
3) UnZip the zip and use iTunes (for Windows) "Add File to Library..." menu to navigate in zip folder to the instrumented iOS Device application [XXXXXXXX.ipa in “instrumented/iOS Device” folder]
4) Plug in iDevice to Windows using USB, select the App, click associated "Install" button, then "Sync" iTunes.
5) Now test as usual...
Thanks
MTWW in Worklight 6.1.0.0 and 6.1.0.1 (to be released, soon) does not support iOS 7.1.
Work is under way to provide support in a future release of Worklight.
I am having this desktop project which contains a native extension, when I run it there is absolutely no problem, and the native extension works fine,
But when I try to export a release build It shows this error message "Native extensions are being used in the project but are not supported by the AIR package type. Runtime issues can occur."
Flash Builder 4.6, Windows 7 x64
I have seen some answers, saying it's a bug on 4.6, so I tried on 4.7 and still having the same error
To use ANEs on the desktop, you need to publish the app as a native installer rather than an AIR installer.
On the first page of the publish wizard there is an option "Export as:" - select "Signed native installer".
You will also need to amend the app descriptor file to include the extended desktop as a profile:
<supportedProfiles>extendedDesktop</supportedProfiles>
After using the "iPhone Configuration Utility" program to install IPA applications to my iPhone on the go, I wondered how this process worked. Within a few Google searches, I found out about "MobileDevice.framework" and the "MobileDevice Library" connected to it. After reading an article of all the Known Functions in the library, I found one called "AMDeviceInstallApplication". I thought this would work once I saw install, but I'm currently perplexed on how to use it.
TL;DR I have IPA files and I want to make an Xcode program (for Mac) that installs the IPA's application to a connected iOS device when a button is pressed.
Also, don't worry about the application not being signed correctly. It is signed with a provisioning profile installed on devices [the application] will be used with.
If you're still interested in this problem I've written a blog entry on how to install apps on a connected iPad / iPhone without using Xcode or iTunes.
This method allows you to run a Terminal command to install an iPA file.
http://pervasivecode.blogspot.co.uk/2012/06/install-ios-app-ipa-file-without-xcode.html
I suppose you could bundle up the terminal commands in your application and use it that way?
I found a simple way to install iPa file to real iPhone or iPad:
Connect iPhone to Mac via USB and follow the below steps:
Steps to follow:
Open Xcode
Click on Window
Select Devices and Simulators
Drag and drop the IPA files into it
App got installed on the iPad