Hi There,
Just upgraded from a previous version of B4A (11.20) and I was aware of the problem with OkHTTPUtils2.
I have a library (b4a created with compile to library) that comunicates with the rest server api using OKHTTPUtils2 (I was using the previous version before)
This library have many subs reflecting each possible calling from the server api.
This is everywhere in my big source code.
I create an object with my library, in one specific place:
then I use it like this: Server.DoLogin
This is everywhere... It is called from other modules either.
Inside my yClientIssuer (where the api is called)
I cannot change to B4Xpages... this is a huge project and the concept of pages does not fit for this project (this is a POS system, it is static layout)
Just upgraded from a previous version of B4A (11.20) and I was aware of the problem with OkHTTPUtils2.
I have a library (b4a created with compile to library) that comunicates with the rest server api using OKHTTPUtils2 (I was using the previous version before)
This library have many subs reflecting each possible calling from the server api.
This is everywhere in my big source code.
I create an object with my library, in one specific place:
B4X:
'Class module
Sub Class_Globals
Private FClientIssuer As yClientIssuer
end sub
Public Sub Initialize(ApkName As String, ConnectionType As Int, AppType As String)
FClientIssuer.Initialize()
Public Sub Server As yClientIssuer
Return FClientIssuer
End Subthen I use it like this: Server.DoLogin
This is everywhere... It is called from other modules either.
Inside my yClientIssuer (where the api is called)
B4X:
Wait For (QServer) JobDone(job As HttpJob)
If QServer.Success Then
JobDone(job)
End IfI cannot change to B4Xpages... this is a huge project and the concept of pages does not fit for this project (this is a POS system, it is static layout)