When I done some changes in main.Dart of simple HelloWorld program ,new changes are not reflecting in my mobile.Old UI changes are reflecting.I have restarted my visual studio editor, uninstall app.Still old UI changes are reflecting.
Visual studio provide terminal in bottom,
type Flutter run
then you will see ..
Launching lib/main.dart on SM G615F in debug mode...
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done 16.8s
✓ Built build/app/outputs/apk/debug/app-debug.apk.
Syncing files to device SM G615F...
D/GraphicBuffer(24157): register, handle(0xddbb3680) (w:1080 h:1920 s:1088 f:0x1 u:b00)
Syncing files to device SM G615F... 5,356ms (!)
Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h Repeat this help message.
d Detach (terminate "flutter run" but leave application running).
q Quit (terminate the application on the device).
Type r
Initializing hot reload...
Reloaded 0 of 483 libraries in 523ms.
D/GraphicBuffer(24157): register, handle(0xddbb3920) (w:1080 h:1920 s:1088 f:0x1 u:b00)
After that Type R .
Performing hot restart...
Restarted application in 2,067ms.
Changes are reflecting.Issue get resolved
if your code don't reflect on your UI or real device , you can move to master channel of flutter then run flutter clean
you can move to master channel by run in terminal :
flutter channel master
Related
What:
After updating to pretty much all Cypress versions 10.x.x, WebStorm stopped or Cypress stopped opening the correct line number for the below scenarios:
Issue:
Where a test would fail an assertion etc. with link to the line in IDE.
Open In IDE inside specific spec it block .
Inside SCREENSHOT: FAILED_LINE_NUMBER it brings me to that line however that's not the line the test actually failed at.
Similar situation when I click on the link pointed out inside SCREENSHOT: GENERIC_BODY_OPEN_IN_IDE -- clicking the link doesn't bring me to the correct it block.
I am fairly certain this is user error but cannot figure it out.
Setup:
Windows 10
Cypress 10.0.3
WebStorm v221.5921.27
cypress runner > Settings > Device Settings > External Editor = Custom C:\Users\me\AppData\Local\JetBrains\Toolbox\apps\WebStorm\ch-0\221.5921.27\bin\webstorm64.exe
Things I have tried:
Wiping cache inside C:\Users\me\AppData\Local\Cypress\Cache and then running npm i cypress
Reinstalling WebStorm
Images:
FAILED_LINE_NUMBER
GENERIC_BODY_OPEN_IN_IDE
I used to be able to run on android and all of a sudden I am getting this error (see below).
The only thing I recall changing is downgrading "nativescript-ui-listview" to "^7.1.0" and "nativescript-ui-sidedrawer" to "~7.0.0" because it otherwise breaks on ios 12.
Webpack compilation complete. Watching for file changes.
Webpack build done!
Project successfully prepared (android)
Installing on device f180a829...
More than one .apk found in /Users/manuelmaestrini/Programming/spiio-development/spiiomobile/platforms/android/app/build/outputs/apk directory. Using the last one produced from build.
Successfully installed on device with identifier 'f180a829'.
Application com.spiio.mobile is not running on device f180a829.
This issue may be caused by:
* crash at startup (try `tns debug android --debug-brk` to check why it crashes)
* different application identifier in your package.json and in your gradle files (check your identifier in `package.json` and in all *.gradle files in your App_Resources directory)
* device is locked
* manual closing of the application
Unable to apply changes on device: f180a829. Error is: Application com.spiio.mobile is not running.
Any idea what might be? I tried to do --clean, remove node_modules, hooks, platforms, uninstall and reinstall webpack etc but no luck...
I I started a new TizenWearableApp in VS 2019, started the Tizen-Emulator and hit run.
The output from Tizen shows the successful build and that the app is signed with Default Certificates. After that, the last printed line is the full path to the .tpk file and a Microsoft Visual Studio Dialog with "Initializing Debugger"...
stuck state screenshot -> https://imgur.com/a/91sEknd
After that nothing more happens. I can press the cancle button and can then see in the Output the following which didn´t help me:
: <<< Start debugging "org.tizen.example.TizenWearableAppV4" >>>
: Try to terminate running application: org.tizen.example.TizenWearableAppV4
: No application to be terminated: 255
WARNING: Your data are to be sent over an unencrypted connection and could be read by others.
pushed org.tizen.example.TizenWearableAppV4-1.0.0.tpk 0% 0KB 0KB/s
pushed org.tizen.example.TizenWearableAppV4-1.0.0.tpk 100% 19KB 0KB/s
1 file(s) pushed. 0 file(s) skipped.
D:\repos\Tizen\TizenWearableAppV4\TizenWearableAppV4\bin\Debug\tizen40\org.tizen.example.TizenWearableAppV4-1.0.0.tpk 447KB/s (19702 bytes in 0.042s)
path is /home/owner/share/tmp/sdk_tools/org.tizen.example.TizenWearableAppV4-1.0.0.tpk
processing result : Operation not allowed [-4] failed
Package found on the target system: "lldb-3.8.1-i686" (tar.gz)
: Launching org.tizen.example.TizenWearableAppV4
: 'org.tizen.example.TizenWearableAppV4' is dependent on 'org.tizen.example.TizenWearableAppV4-1.0.0.tpk'.
: ... launch failed
I hope anybody can help me to fix that problem (i got it already working a few month back on this machine).
Thanks in advance.
https://github.com/Samsung/build-task-tizen/blob/master/doc/tizen.net.sdk-signing-tpk.md
Here is the page that helped me. I had the same problem but don't want to build from tizen.bat every time. The solution in the above document that worked for me was to close Visual Studio and open the *.csproj file in my solution then add the following replacing with the directory of the certificates I created and my passwords:
<PropertyGroup>
<AuthorPath>author_test.p12</AuthorPath>
<AuthorPass>author_test</AuthorPass>
<DistributorPath>tizen-distributor-signer.p12</DistributorPath>
<DistributorPass>tizenpkcs12passfordsigner</DistributorPass>
</PropertyGroup>
Just put it below any other Property Group tags. Open Visual Studio again and it should build using the certificate.
Faced same. The reason was in certificate signed with wrong distributor - for physical devices (not emulated) you need Samsung distributor certificate. You need to do:
Install Samsung Certificate Extension in Tizen package manager
Open Certificate manager
Run certificate profile wizard and select Samsung option
Follow wizard
Refer to https://stackoverflow.com/a/40755444/4165898
I have problem with Xcode.. if I want to run any playground even simple code like : print("Hello "), it is not working,
some time stuck on 'running' and won't run the code,
I tried to reinstalling and delete xcode files ...
but it's still not working
this is the message that appears:
( Failed to launch process. Unable to lookup in current state: Shutting Down )
..
Failed to launch process. Unable to lookup service com.apple.CoreSimulator.host_support: 0xfffffecc )
it's last version 8.2.1(8C1002)
This fixed it for me:-
Go to menu Xcode->Preferences->Components then select and install the most recent Simulator.
MyPlayground is constantly syncing to iCloud.
Sometimes because of buggy behavior or poor connection is stucks on "Running"
Just go to:
System Preferences - Apple ID - Apps on this Mac using iCloud- iCloud Drive - Options- And then uncheck "Playground"
That little trick prevents syncing and resolves the frozen "Running".
I'm working on an iOS project in Xcode 6.1 (which includes an app extension, in case that's relevant). When I try to run the project on Xcode, however, it doesn't actually run the project -- it just says its finished running seconds after "Running [My target]" appears in the Xcode window's toolbar. A (2) in a grey circle appears to the left of the running text before the app "finishes," on successful runs there is usually a (3).
If I delete the app from the device and try to build and run it again, Xcode claims that it finished running without ever installing it in the first place.
In the console of my computer, I can see the following messages:
10/23/14 9:56:33.045 AM Xcode[86586]: AMDeviceSecureInstallApplicationBundle (thread 0x11e05f000): no old package to delta against, falling back to old skool install
10/23/14 9:56:33.045 AM Xcode[86586]: AMDeviceSecureInstallApplicationBundle (thread 0x11e05f000): Blasting the bundle over to the device in an old skool way
10/23/14 9:56:37.949 AM Xcode[86586]: AMDErrorForMobileInstallationCallbackDict (thread 0x11c59e000): GOT AN ERROR 0xe800003a
10/23/14 9:56:37.956 AM Xcode[86586]: SZConduit: _MonitorResultDispatchFunction:140 (0x0x11c59e000): Got error from service: InstallationFailed
10/23/14 9:56:37.956 AM Xcode[86586]: _AMDeviceTransferAndInstall (thread 0x11e05f000): SZConduitSendPathWithPreflight failed: 0xe8008017
10/23/14 9:56:37.960 AM Xcode[86586]: writeDictToFile:1258 ==== Successfully wrote Manifest cache to /var/folders/yt/lbzml8ns3f5dfg7chpk14s2h0000gp/C/com.apple.DeveloperTools/6.1/Xcode/af8b53723f8db55690c776f7ae336036/2031be7d6eb56fd1d8e5c85034f9500facb31def/ManifestCache.plist
10/23/14 9:56:37.961 AM Xcode[86586]: AMDeviceSecureInstallApplicationBundle (thread 0x11e05f000): returning 0xe8008017
No one else working on this project has this issue. Occasionally I see an error message with something like "Can't run, a signed resource is missing or has been altered," but this is pretty rare.
I've tried reinstalling Xcode, this does nothing.
Deleting Derived data fixes the issue, but I have to delete it after every run or the problem reappears. This is pretty inconvenient, so I'm looking for a more permanent fix.