Closed Kumaravinash9 closed 3 years ago
https://drive.google.com/file/d/1_3LTBwK_PDZDksTIf5gBAio5CNWmpWma/view?usp=sharing @defnax and @obrasero @csoler can you please test it. Is it working or not.
OK, i downloaded it. Now i go to sleep. tomorrow i will test.
As the main-problem until now in my testings is the frequently and quick service-down this will than be the test i can provide. Is the checkin "handling-down" restarting the service? Also i think, the reason why the service frequently shuts down if the rs-mobile is started should be determined.
doesnt not works like your screenshot, but im using bluestacks emulator. i see few milliseconds something not more
doesnt not works like your screenshot, but im using bluestacks emulator. i see few milliseconds something not more
I am asking are you able to login or not. And Please check the friend identity as well as
doesnt not works like your screenshot, but im using bluestacks emulator. i see few milliseconds something not more
can you please send me the screenshot
doesnt not works like your screenshot, but im using bluestacks emulator. i see few milliseconds something not more
I am asking are you able to login or not. And Please check the friend identity as well as
login works but slow, im waiting 1-2 minutes
doesnt not works like your screenshot, but im using bluestacks emulator. i see few milliseconds something not more
I am asking are you able to login or not. And Please check the friend identity as well as
login works but slow, im waiting 1-2 minutes
About Create profile
but i must do via mouse click to get that effect it doesnt stays long , on friends locations doesnt works
but i must do via mouse click to get that effect it doesnt stays long , on friends locations doesnt works
In Friend_location, It should work
create profile stays endless like same before, but this after closing rs mobile and restart the new profile is not generated
i come till create identity
create profile stays endless like same before, but this after closing rs mobile and restart the new profile is not generated
i come till create identity
Actually it will work. Intially it take some time. I have tested it
i get now work distant chat, but you never know if the chat tunnel etablished in the distant chats with contacts.
we need more infos:
i found a issue when leaving the distant chat on rs mobile the tunnels seems stays active, i see online the chat on my rs desktop going sleep
@csoler did you check this App
it will come a working version with profile generation? not easy to test the rs-mobile with profile generation issues
this word is to big use short text as possible
Hi i has no succes more with apk, attempting to test via the emulator run from flutter
but gets issues where get the package or how to install it?
C:\Users\ProBook\Documents\GitHub\retroshare-mobile>flutter run No supported devices connected. The following devices were found, but are not supported by this project: Chrome (web) • chrome • web-javascript • Google Chrome 92.0.4515.131 Edge (web) • edge • web-javascript • Microsoft Edge 91.0.864.70 If you would like your app to run on web, consider running
flutter create .
to generate projects for these platforms.C:\Users\ProBook\Documents\GitHub\retroshare-mobile>flutter devices 3 connected devices:
ONEPLUS A5000 (mobile) • emulator-5554 • android-x86 • Android 7.1.1 (API 25) Chrome (web) • chrome • web-javascript • Google Chrome 92.0.4515.131 Edge (web) • edge • web-javascript • Microsoft Edge 91.0.864.70
C:\Users\ProBook\Documents\GitHub\retroshare-mobile>flutter run Because retroshare depends on openapi from path which doesn't exist (could not find package openapi at "..\openapi-dart-retroshare-api-wrapper"), version solving failed. Running "flutter pub get" in retroshare-mobile... pub get failed (66; Because retroshare depends on openapi from path which doesn't exist (could not find package openapi at "..\openapi-dart-retroshare-api-wrapper"), version solving failed.)
C:\Users\ProBook\Documents\GitHub\retroshare-mobile>
found the packages, but running from flutter console is slow? or i can run from android studio directly retroshare-mobile?
ok i found on android studio i need create virtual device but i started via chrome the rs-mobile
from console get no sucess to find a emultor device
Yes, you can
run from android studio directly retroshare-mobile?
In Menu "run" select "run" for release building with run or debug for debug building with run.
The first call is "slow" as the srces must all get build. Follow-up calls to run or debug - if you dont change in code- will be quicker. But nevertheless if you call debug its will be also slower running caused by the debug-instrumentation included.
But. if you only want repeatadly start the rs-mobile without interest in the debug-output or breakpoint setting you also can just start the installed apk-s without flutter or android. The traces are anyway avail.
I myself only test with usb-plugged in physical device.
@defnax i found on android studio i need create virtual device ... get no sucess to find a emultor device image
Did you follow my description to setup the android/-studio/flutter? The steps worked to me. i tested them an 2 different laptops.
At which step got it "out-of-order" Maybe i must adapt the description to be clearer or better?
@defnax i found on android studio i need create virtual device ... get no sucess to find a emultor device image
Did you follow my description to setup the android/-studio/flutter? The steps worked to me. i tested them an 2 different laptops.
At which step got it "out-of-order" Maybe i must adapt the description to be clearer or better?
you has removed the howto PR, without it was merged
@defnax i found on android studio i need create virtual device ... get no sucess to find a emultor device image
Did you follow my description to setup the android/-studio/flutter? The steps worked to me. i tested them an 2 different laptops. At which step got it "out-of-order" Maybe i must adapt the description to be clearer or better?
you has removed the howto PR, without it was merged
I can help you with android studio and emulator
@defnax i found on android studio i need create virtual device ... get no sucess to find a emultor device image
Did you follow my description to setup the android/-studio/flutter? The steps worked to me. i tested them an 2 different laptops. At which step got it "out-of-order" Maybe i must adapt the description to be clearer or better?
you has removed the howto PR, without it was merged
Ouhh... that was not intended. Seems than a side effect of my the checkin from my local repo-clone. I try to correct it..., meaning the unintended close of the push rew to reopen..... one moment.
In Menu "run" select "run" for release building with run or debug for debug building with run.
yes used the release run
if you only want repeatadly start the rs-mobile without interest in the debug-output or breakpoint setting you also can just > > start the installed apk-s without flutter or android. where is the installed apk's? on Android studio?
I myself only test with usb-plugged in physical device.
i need buy next month a testing android phone for rs mobile.
Ypu can use emulator then you donot have to buy the mobile.
Ypu can use emulator then you donot have to buy the mobile.
without a real phone cant test how is it useable then on a notebook emulator, it different via phone
OK. howto hopefully back again.
hope a useable apk will be published with a fix the profile creation issue, i only tested the other ways how to run rs-mobile from flutter or android studio useful for new android devs. Lets see next days and weeks.
hope a useable apk will be published with a fix the profile creation issue, i only tested the other ways how to run rs-mobile from flutter or android studio useful for new android devs. Lets see next days and weeks.
THIS WILL FIX SOON. I AM CURRENTLY WORKING ON IT. ON WEDNESDAY IT WILL FIX .
Emulator, by the way is to slow to me on my laptops :).
hope a useable apk will be published with a fix the profile creation issue
The problems i showed with the trace files in my tests do not only happen on profile creation. They happen all service actions round in my tests. If i was lucky to get successful behind profile generation i got the same game at - for exc. - identity creation.
As service uninstall and reinstall removes the old profile data, and i tested with different service versions i'm actually completely sticked in profile creation. So this is just the first border to take. I press all thumbs to @Kumaravinash9 - don't know the correct english phrase for it - ;)
As Service unsinstall and reinstall removes the old profile data, and i tested with different service versions i actually completly stick in profile creation. So this is just the first border to take.
me too no sucess more and updating/reinstalling service you losing your profile, at the moment its bad to update your service all is lost.
Yes, it's a hard way through the tests. Especially if you try to reproduce the test-scenarion exacty on retesting and a new service is involved/to install. It's for real robust testers ;) But I'm afraid @Kumaravinash9 will solve it and testing will be terribly easy. ;)
A question comes into mind @Kumaravinash9 . i looked through the code and it seems to me that in profile creation the code should catch the exceptions and at least come out with the error-dialog that the service may be down. But in my tests none of the both exceptions allways got catched and so never showed this problem hint. They just always ended in an endless working profile-generation.
What is the reason for this?
A question comes into mind @Kumaravinash9 . i looked through the code and it seems to me that in profile creation the code should catch the exceptions and at least come out with the error-dialog that the service may be down. But in my tests none of the both exceptions allways got catched and so never showed this problem hint. They just always ended in an endless working profile-generation.
What is the reason for this?
Because retroshare service doesnot give the response of your request that why it moving forever.
Yes, but it results into an exception, and to me your code looks like a catch-all. That's what i don't understand. Also i debug the code line for line it just jumps with the exception out of the method completly ignoring both of your exception catch blocks, the typed one as well as the catch(e) (catch all?)-version.
To be more clear, -i'm talking about signup_screen the try gets catched with:
try{.... } on HttpException catch (err) { var errorMessage = 'Authentication failed'; errorShowDialog( "Auth Failed", 'Something went wrong', context); } catch (e) { errorShowDialog('Retroshare Service Down', 'Please ensure retroshare service is not down!', context); }
The try comes back with a socket or an incomplete header exception. but stepping through the debugger shows that these exceptions get noct catched by at least the 2. catch, the cacth(e).
To be more clear, -i'm talking about signup_screen the try gets catched with:
try{.... } on HttpException catch (err) { var errorMessage = 'Authentication failed'; errorShowDialog( "Auth Failed", 'Something went wrong', context); } catch (e) { errorShowDialog('Retroshare Service Down', 'Please ensure retroshare service is not down!', context);
}The try comes back with a socket or an incomplete header exception. but stepping through the debugger shows that these exceptions get noct catched by at least the 2. catch, the cacth(e).
maybe you can try the old rs mobile from b1rd if it has the same issue? with profile creation? i never hear from @b1rdG that there are profile creation issues. or its a new bug from this year https://gitlab.com/b1rdG/retroshare-android-flutter-app
I'm not searching with this a way around the creation bug. I'm searching to understand the code, especially the working of the flutter exception in this case. So a code-understanding question. Or what do i understand wrong in the flutter-exception-catch code semantic above, as it obviously does not do what i would await if i see such a code.
To be more clear, -i'm talking about signup_screen the try gets catched with:
try{....
} on HttpException catch (err) {
var errorMessage = 'Authentication failed';
errorShowDialog(
"Auth Failed", 'Something went wrong', context);
} catch (e) {
errorShowDialog('Retroshare Service Down',
'Please ensure retroshare service is not down!', context);
} The try comes back with a socket or an incomplete header exception. but stepping through the debugger shows that these exceptions get noct catched by at least the 2. catch, the cacth(e).
Showing exception to user that makes no sense that'why I didn't return the err there
To be more clear, -i'm talking about signup_screen the try gets catched with:
try{.... } on HttpException catch (err) { var errorMessage = 'Authentication failed'; errorShowDialog( "Auth Failed", 'Something went wrong', context); } catch (e) { errorShowDialog('Retroshare Service Down', 'Please ensure retroshare service is not down!', context);
} The try comes back with a socket or an incomplete header exception. but stepping through the debugger shows that these exceptions get noct catched by at least the 2. catch, the cacth(e).maybe you can try the old rs mobile from b1rd if it has the same issue? with profile creation? i never hear from @b1rdG that there are profile creation issues. or its a new bug from this year https://gitlab.com/b1rdG/retroshare-android-flutter-app
This code have some bug and will not work properly with new retroshare service because some retroshare api has been discarded now.
To be more clear, -i'm talking about signup_screen the try gets catched with: try{.... } on HttpException catch (err) { var errorMessage = 'Authentication failed'; errorShowDialog( "Auth Failed", 'Something went wrong', context); } catch (e) { errorShowDialog('Retroshare Service Down', 'Please ensure retroshare service is not down!', context); } The try comes back with a socket or an incomplete header exception. but stepping through the debugger shows that these exceptions get noct catched by at least the 2. catch, the cacth(e).
Showing exception to user that makes no sense that'why I didn't return the err there
Sorry for anoying you, yes my english is not good. I will try again.
I see in your code the cited sequence try{...}..catch(e){...} And in the try-block an exception happens but the catch-part does not catch this exception and instead leaving it unhandled through. I try to understand flutter/dart-semantic in exception handling and wonder why the exception gets not catched at least by your "catch(e)", which than should result, as i understand this code, in an errorShowDialog('Retroshare Service Down'..). This error-dialog does not pop up and debugging also shows, that the exception just gets not catched by the given catch-block. I wonder why. i wonder how...dadada ;) it is not catched, where is my misunderstanding of the flutter/dart try-catch in this code?
Actually we are not catching the exception where we are doing http request for signup. https://github.com/RetroShare/retroshare-mobile/blob/de02052facc01fdbb27444ab310669472c562966/lib/services/account.dart#L84
Socket exception comes only when your service will not accept the request. Means retroshare service deny the http request
Ouhh i see, my english is realy a problem.
Your code above:
try{...} on HttpException catch (err){do1} catch(e){do2}
I interpret it as: if an http-exception comes up in try{...} catch it and process do1. if any other type of exception comes up in try... catch it and process do2.
Any misinterpretation in it?
Now in fact in try i see in my tests come 2 exceptions up: e1)Sometimes a the socket-exception, e2) actual mostly the "Connection closed before full header was received" exception.
Now if for exc. e2 is a Http-exception it should get catched by onHttp.. and "do1" should get processed. If it is not an http-exception than - following my interpretation above - it should get catched(e) and "do2" should get processed. Fact is: none of both get processed in e2-case, the e2 just gets not catched.
So what is wrong with my above interpretation, why can the exception go out without beeing catched?
Ahhh.. in now looked in a dart-artikle about dart exception and think i got it: The signup in your try-code is an async method which is called in your code without the "await"-keyword. Thats why the exception catch has no effect on exceptions coming while processing signup. Without await the catch block are only effecting the async-method-initiation.
==> i will try and test-wise add an await to see if then do2 gets processed on the "closed before full header" exception.... or if i continue to misunderstand.
OK. tested it to see if i now understand the cause but instead of using await by not waiting and instead using error-callback like i checked in: https://github.com/obrasero/retroshare-mobile/commit/acbb1fefb67ca42ac8670e0b1f475b487b92fdb0 this way:
account_signup.signup(usernameController.text, passwordController.text, nodeNameController.text) .onError((e,_){errorShowDialog('Retroshare Service Down' ,'Please ensure retroshare service is not down!', context);});
and now i get the errordialog and need not caling signup in synchroneous way.
OK. tested it but instead of using await by not waiting and instead using error-callback like i checked in:
Await is used whatever place is needed. Can you please point me out where is not added
I showed it already to you in my code citations. There is onyl one place in your signup_screen.dart code where an on HttpException catch is done. But my checkin above should also show the codeplace i was talking about in my dart-learning-and-understanding questions to you.
Fix:
24
36
37