thought this issue was resolved, but it's back just as bad as before. here's the issue in VCL Cloud Pack that just 'went away' when using XE10.2:
Now exactly the same/similar thing is happening when using FMX Cloud Pack and trying to authorise from within a dll:
// Authorise Dropbox
If not(TMSDropbox.Connect) then
if signinTimeout then
raise Exception.Create(inttostr(Ord(ERR_DBXAUTHTIMEOUT)))
else
raise Exception.Create(inttostr(Ord(ERR_DBXAUTHFAIL)));
- With ExternalBrowser False
- Execute .CONNECT
- Falls straight through to error condition
- BUT the internal browser appear
- The details are entered
- The INI file is created, but empty
- I get the message ...you can close the browser window now... ie. the software doesn't know it's using an internal browser
- If I user an external browser exactly the same
If I use the code that does a DOAUTH the same, nothing is recognised by TMS code:
TMSDropbox.LoadTokens;
Authorised := TMSDropbox.TestTokens;
if not(Authorised) then
begin
TMSDropbox.RefreshAccess;
Authorised := TMSDropbox.TestTokens;
if not(Authorised) then
TMSDropbox.DoAuth;
end;
DOAUTH does nothing, ie. there is no browser popped up (external or internal).
Is there a fix, I don't want to go back to named pipes passing credentials around, that's just garbage....
Anyone have any ideas?