Unhandled Exception: PlatformException(Exception encountered, read, javax.crypto.BadPaddingException: error:1e000065:Cipher functions:OPENSSL_internal:BAD_DECRYPT #161

JAICHANGPARK · 2020-09-23T01:16:22Z

How to fix this problem?

E/flutter (29195): [ERROR:flutter/lib/ui/ui_dart_state.cc(177)] Unhandled Exception: PlatformException(Exception encountered, read, javax.crypto.BadPaddingException: error:1e000065:Cipher functions:OPENSSL_internal:BAD_DECRYPT
E/flutter (29195): 	at com.android.org.conscrypt.NativeCrypto.EVP_CipherFinal_ex(Native Method)
E/flutter (29195): 	at com.android.org.conscrypt.OpenSSLCipher$EVP_CIPHER.doFinalInternal(OpenSSLCipher.java:570)
E/flutter (29195): 	at com.android.org.conscrypt.OpenSSLCipher.engineDoFinal(OpenSSLCipher.java:351)
E/flutter (29195): 	at javax.crypto.Cipher.doFinal(Cipher.java:1741)
E/flutter (29195): 	at com.it_nomads.fluttersecurestorage.ciphers.StorageCipher18Implementation.decrypt(StorageCipher18Implementation.java:91)
E/flutter (29195): 	at com.it_nomads.fluttersecurestorage.FlutterSecureStoragePlugin.decodeRawValue(FlutterSecureStoragePlugin.java:163)
E/flutter (29195): 	at com.it_nomads.fluttersecurestorage.FlutterSecureStoragePlugin.read(FlutterSecureStoragePlugin.java:144)
E/flutter (29195): 	at com.it_nomads.fluttersecurestorage.FlutterSecureStoragePlugin.access$300(FlutterSecureStoragePlugin.java:29)
E/flutter (29195): 	at com.it_nomads.fluttersecurestorage.FlutterSecureStoragePlugin$MethodRunner.run(FlutterSecureStoragePlugin.java:197)
E/flutter (29195): 	at java.lang.Thread.run(Thread.java:764)
E/flutter (29195): , null)

The text was updated successfully, but these errors were encountered:

bettdouglas · 2020-09-23T10:14:29Z

I'm also experiencing the same problem

message_codecs.dart in StandardMethodCodec.decodeEnvelope at line 572 platform_channel.dart in MethodChannel._invokeMethod at line 161 Called from: <asynchronous suspension> flutter_secure_storage.dart in FlutterSecureStorage.read at line 30

PlatformException(Exception encountered, read, javax.crypto.BadPaddingException: error:1e000065:Cipher functions:OPENSSL_internal:BAD_DECRYPT
at com.android.org.conscrypt.NativeCrypto.EVP_CipherFinal_ex(Native Method)
at com.android.org.conscrypt.OpenSSLCipher$EVP_CIPHER.doFinalInternal(OpenSSLCipher.java:596)
at com.android.org.conscrypt.OpenSSLCipher.engineDoFinal(OpenSSLCipher.java:363)
at javax.crypto.Cipher.doFinal(Cipher.java:2055)
at c.c.a.a.b.b(:8)
at c.c.a.a.b(:9)
at c.c.a.a.d(:2)
at c.c.a.a.onMethodCall(:11)
at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(:2)
at io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(:5)
at io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(:2)
at android.os.MessageQueue.nativePollOnce(Native Method)
at android.os.MessageQueue.next(Unknown Source:19)
at android.os.Looper.loop(Unknown Source:64)
at android.app.ActivityThread.main(Unknown Source:107)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(Unknown Source:11)
at com.android.internal.os.ZygoteInit.main(Unknown Source:274)
)

bettdouglas · 2020-09-25T03:43:25Z

I used this workaround by adding
<application ... android:allowBackup="false" android:fullBackupContent="false">

to AndroidManifest.xml

sheychan31 · 2020-09-27T20:32:53Z

I used this workaround by adding
<application ... android:allowBackup="false" android:fullBackupContent="false">

to AndroidManifest.xml

@bettdouglas this doesnt seem to work anymore.

sheychan31 · 2020-09-27T20:33:28Z

I encounter this too when running the app for the 2nd time.

dara1chan · 2020-09-28T08:30:32Z

I got the same problem.

HemilTheRebel · 2020-09-28T10:33:06Z

I have the same problem. But the bug only triggers some of the time. I always reproduce it
This is my stacktrace:

PlatformException(Exception encountered, read, javax.crypto.BadPaddingException: error:1e000065:Cipher functions:OPENSSL_internal:BAD_DECRYPT
I/flutter (30164): 	at com.android.org.conscrypt.NativeCrypto.EVP_CipherFinal_ex(Native Method)
I/flutter (30164): 	at com.android.org.conscrypt.OpenSSLCipher$EVP_CIPHER.doFinalInternal(OpenSSLCipher.java:602)
I/flutter (30164): 	at com.android.org.conscrypt.OpenSSLCipher.engineDoFinal(OpenSSLCipher.java:365)
I/flutter (30164): 	at javax.crypto.Cipher.doFinal(Cipher.java:2055)
I/flutter (30164): 	at com.it_nomads.fluttersecurestorage.ciphers.StorageCipher18Implementation.decrypt(StorageCipher18Implementation.java:91)
I/flutter (30164): 	at com.it_nomads.fluttersecurestorage.FlutterSecureStoragePlugin.decodeRawValue(FlutterSecureStoragePlugin.java:163)
I/flutter (30164): 	at com.it_nomads.fluttersecurestorage.FlutterSecureStoragePlugin.read(FlutterSecureStoragePlugin.java:144)
I/flutter (30164): 	at com.it_nomads.fluttersecurestorage.FlutterSecureStoragePlugin.access$300(FlutterSecureStoragePlugin.java:29)
I/flutter (30164): 	at com.it_nomads.fl

HemilTheRebel · 2020-09-28T11:53:29Z

I downgraded to 3.3.3 and the issue disappeared.
Change pubspec.yaml to flutter_secure_storage: 3.3.3

rodrigo-martins-ifood · 2020-09-28T18:48:38Z

I'm having the same problem on 3.3.3

Repost: Version 3.3.4 with

Seem to solve the problem for me.

iNima · 2020-09-29T01:32:22Z

I added <application ... android:allowBackup="false" android:fullBackupContent="false"> with 3.3.4 but the same error is still there.
I had to change back to 3.3.2 and the problem solved.

Andrew-Bekhiet · 2020-09-29T13:38:24Z

I got the same problem with 3.3.3 and 3.3.4, but when downgraded to 3.3.2 it works fine for me

sydneyagcaoili · 2020-09-29T19:46:55Z

Used 3.3.2 then 3.3.1+1 it's still a problem..

Andrew-Bekhiet · 2020-09-29T21:03:14Z

@sydneyagcaoili Double check if the version also changed in the pubspec.lock file

sandeeppatel1986 · 2020-09-30T04:21:32Z

@Andrew-Bekhiet I have same issue also tried with deleting pubspec.lock file. Any further solution.
Flutter 1.20.2
flutter_secure_storage: ^3.3.2

Device Samsung S10+(Android 10)

iNima · 2020-09-30T07:18:46Z

@sandeeppatel1986 Just for double-checking, go to your .pub_cache/hosted/pub.dartlang.org/ folder and check the version number of flutter_secure_storage. Make sure that the folder name is flutter_secure_storage-3.3.2

mogol · 2020-09-30T07:33:01Z

If anyone has consistent failures, could you please provide a steps to reproduce from scratch?

If you change manifest, I believe you have to delete and then reinstall the app with new manifest, simple relaunch shouldn't help.

HemilTheRebel · 2020-09-30T09:57:20Z

@mogol I haven't tried to reproduce this problem due to my schedule currently. I will try to do it today. I haven't changed the manifest in the file since a long time. I had flutter_secure_storage v3.3.3 and it worked. It was when I upgraded to v3.3.4 that I started seeing this error message. I fixed the error by reverting to v3.3.3. My pubspec.yaml has: flutter_secure_storage: 3.3.3 The fix was removing the caret symbol to select an exact version

ldemyanenko · 2020-10-05T09:48:54Z

I'm having this issue on 3.3.4- 3.3.1 versions with Flutter 1.22. I didn't find any solution. I had to remove this lib from the project

mrevoir · 2020-10-05T16:08:50Z

Roughly 1% of my users are having this problem -- I'm currently using Flutter 1.20.4 and Dart 2.9.2. I haven't found a direct correlation amongst them. I added code at the same time I went from 3.3.3 to 3.3.4 to allow them to report this particular error so it may have been happening before.

@mogol I'll let you know if I'm able to replicate in a demo project.

For those moving to another library, what did you choose?

koskimas · 2020-10-06T20:45:25Z

This is randomly happening for me too. The payload that causes it for me is a largeish json string that I unfortunately cannot share here.

I appreciate this great library, and thank you for all the work you've done for it. But unfortunately, this kind of bug is a no-go for this kind of a library that we must be able to trust. I realize that you are probably developing this library on your spare time, but I hope you find time to fix this soon.

koskimas · 2020-10-06T21:48:51Z

Here's a reproduction.

Create a new app using flutter create

Replace the content of main.dart with this:

import 'dart:math';

import 'package:flutter/material.dart';
import 'package:flutter_secure_storage/flutter_secure_storage.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Secure storage bug',
      theme: ThemeData(
        primarySwatch: Colors.blue,
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: MyHomePage(title: 'Secure storage bug'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);
  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  final secureStorage1 = FlutterSecureStorage();

  Future<void> write() async {
    for (int i = 0; i < 100; ++i) {
      secureStorage1.write(key: 'TEST1', value: 'a');
      secureStorage1.write(key: 'TEST2', value: 'a');
    }
  }

  Future<void> read() async {
    for (int i = 0; i < 100; ++i) {
      secureStorage1.read(key: 'TEST1');
      secureStorage1.read(key: 'TEST2');
    }
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            RaisedButton(
              child: Text('write'),
              onPressed: write,
            ),
            RaisedButton(
              child: Text('read'),
              onPressed: read,
            ),
          ],
        ),
      ),
    );
  }
}

Click write and then read (may need to do that couple of times) and you'll get the error.

So this seems to happen when I run multiple read/write operations in parallel.

koskimas · 2020-10-06T22:06:09Z

A temporary workaround would be to serialize all calls to this library and to only use one FlutterSecureStorage instance per app. Something like this:

class AsyncMutex {
  Completer<void> _completer;

  Future<void> lock() async {
    while (_completer != null) {
      await _completer.future;
    }

    _completer = Completer<void>();
  }

  void unlock() {
    assert(_completer != null);
    final completer = _completer;
    _completer = null;
    completer.complete();
  }
}

class SecureStorage {
  static const _secureStorage = FlutterSecureStorage();
  static final _mutex = AsyncMutex();

  Future<String> read({String key}) async {
    try {
      await _mutex.lock();
      return await _secureStorage.read(key: key);
    } finally {
      _mutex.unlock();
    }
  }

  Future<void> write({String key, String value}) async {
    try {
      await _mutex.lock();
      await _secureStorage.write(key: key, value: value);
    } finally {
      _mutex.unlock();
    }
  }
}

koskimas · 2020-10-06T23:13:39Z

Looking at the android code, it seems that it's all completely thread-unsafe. this method is run in a separate thread for each call, and there's no synchronization whatsoever for any method calls except for the ensureInitStorageCipher method.

Thread safety was destroyed in this commit

Tommimon · 2020-10-07T01:35:27Z

I'm developing two very similar apps, both using secure storage.

Somehow I encountered this problem in only one of those two apps. I tried all the fixes in this issue but none of those worked for me.
I tried reinstalling secure storage and now both my apps have this issue :(

I really need this package for my project, any alternative?

mogol · 2020-10-07T04:20:20Z

@koskimas thanks for repro case 🎉 , I was looking for it quite a while. Let me try it 👍

koskimas · 2020-10-07T07:08:29Z

@mogol No problem! Took me a good while too 😅

I think many of the other issues here in github are caused by the thread safety issues too. The cipher classes are not thread safe, but they are called from different threads for each flutter call. Every time two calls run in parallel, things can easily go wrong.

The correct solution, I think, would be to have only one worker thread in android native code, in which all operations are run. That way the code doesn't lock the android main thread, and the code is thread safe. HandlerThread could be a good solution.

koskimas · 2020-10-08T07:21:10Z

@mogol I'd be happy to provide a PR for fixing the thread safety issues. Are you already working on the fix or should I start?

mogol · 2020-10-08T07:46:10Z

Hey Sami, I was planning to check on the weekends. So if you can do it early 👍 it’s fine. Sent from ProtonMail Mobile

…

On Thu, Oct 8, 2020 at 10:21, Sami Koskimäki ***@***.***> wrote: ***@***.***(https://github.com/mogol) I'd be happy to provide a PR for fixing the thread safety issues. Are you already working on the fix or should I start? — You are receiving this because you were mentioned. Reply to this email directly, [view it on GitHub](#161 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AA2JY7QG3K23KDWIID6SLFLSJVR7NANCNFSM4RWNS3SA).

Sorunome · 2020-10-08T08:06:04Z

A temporary workaround would be to serialize all calls to this library and to only use one FlutterSecureStorage instance per app. Something like this:

class AsyncMutex {
  Completer<void> _completer;

  Future<void> lock() async {
    while (_completer != null) {
      await _completer.future;
    }

    _completer = Completer<void>();
  }

  void unlock() {
    assert(_completer != null);
    final completer = _completer;
    _completer = null;
    completer.complete();
  }
}

class SecureStorage {
  static const _secureStorage = FlutterSecureStorage();
  final _mutex = AsyncMutex();

  Future<String> read({String key}) async {
    try {
      await _mutex.lock();
      return await _secureStorage.read(key: key);
    } finally {
      _mutex.unlock();
    }
  }

  Future<void> write({String key, String value}) async {
    try {
      await _mutex.lock();
      await _secureStorage.write(key: key, value: value);
    } finally {
      _mutex.unlock();
    }
  }
}

If you make the mutex global you can also use multiple instances, in case it is non-trivial to adapt your app to have a single instance for now and you need a quick fix. Of course not having global variables is cleaner code.

postpasspost · 2021-04-14T09:45:21Z

This error happens only in production in the play store. Huawei android 10. Tried this:

If you need fullBackupContent="yes", you can disable backup of prefs used by the plugin.
<?xml version="1.0" encoding="utf-8"?>
<full-backup-content>
    <exclude domain="sharedpref" path="FlutterSecureStorage"/>
</full-backup-content>

But I still get the error. Using flutter_secure_storage: ^4.2.0

komritza · 2021-07-06T17:05:31Z

I am using version 3.3.5 in the production and since few days ago I started getting sentry reports with following error log:

PlatformException
PlatformException(Exception encountered, read, javax.crypto.BadPaddingException: error:1e000065:Cipher functions:OPENSSL_internal:BAD_DECRYPT
	at com.android.org.conscrypt.NativeCrypto.EVP_CipherFinal_ex(Native Method)
	at com.android.org.conscrypt.OpenSSLEvpCipher.doFinalInternal(OpenSSLEvpCipher.java:152)
	at com.android.org.conscrypt.OpenSSLCipher.engineDoFinal(OpenSSLCipher.java:374)
	at javax.crypto.Cipher.doFinal(Cipher.java:2055)
	at c.c.a.b.b.b(Unknown Source:32)
	at c.c.a.a.b(Unknown Source:11)
	at c.c.a.a.d(Unknown Source:7)
	at c.c.a.a.a(Unknown Source:0)
	at c.c.a.a$b.run(Unknown Source:134)
	at android.os.Handler.handleCallback(Handler.java:938)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loop(Looper.java:246)
	at android.os.HandlerThread.run(HandlerThread.java:67)
, null)

I tried to reproduce the bug, and I manage to do it. Devices that I have tested it Samsung s9 and Samsung s10e => error, Huawei P20 Pro is working and not crashing.
As mentioned above

Installing production App from the PlayStore
Login ( storing some data with FlutterSecureStorage, e.g. token)
Close the App
Uninstalling the App
Install the production app from the PlayStore again
Login -> Error occurs
app got frozen on the splash screen and I got an instant sentry report. App stopped completely working...
Then I have installed the app from VS code and it started working again, but I got this log in my terminal:

D/FlutterSecureStoragePl( 7250): Initializing StorageCipher
I/fluttersecurestorage( 7250): Creating keys!
I/fluttersecurestorage( 7250): Initializing
I/fluttersecurestorage( 7250): Generating key pair
E/KeyStore( 7250): generateKeyInternal failed on request -68
D/CertificatePolicyCache( 7250): Creating new instance of CertificatePolicyCache myUid: 10444 callingUid: 10444
D/CertificatePolicyCache( 7250): readVariables type: null userId: 0
D/FlutterSecureStoragePl( 7250): StorageCipher initialization complete

I don't know if this log is helpful, but this is actually a really huge bug.

dluanoliveira1 · 2021-07-22T01:22:40Z

Hey guys, the problem might be setting a key as empty String, at least for me that was it. I know the thread is closed, by anyways, it could help someone else.

loonix · 2021-07-23T10:03:30Z

I think @dluanoliveira1 got it, for example I am using this plugin and at the start of the app I am reading a value that might be stored. But when I first start the app (after 1st install) there are no keys registered yet, so it gives back that BAD DECRYPT error when it tries to read a key that does not exist.

DineshKachhot · 2021-08-20T13:42:24Z

I am still facing the same issue in release build, I am using flutter_secure_storage: ^4.2.0

appu-sm · 2021-09-07T12:41:55Z

I'm still facing the issue in 4.2.1 and none of the above solutions work, its surprising, a package of 99% popularity is still having the issue reopened again and again :-(

romreed · 2021-10-15T09:27:48Z

I have same issue with flutter_secure_storage: ^4.2.0 in Android 11 on samsung s20.

rsmaximiliano · 2021-10-24T16:48:08Z

Same issue with flutter_secure_storage: ^4.2.0

matthewrice345 · 2021-11-04T15:07:35Z

Just ran into this issue with a Google Pixel 6 Pro tried with:
flutter_secure_storage: ^5.0.0-beta.5 and
flutter_secure_storage: ^4.2.0

kjawadDeveloper2 · 2021-11-12T10:47:48Z

I am also facing this error.

jesusmartinezd · 2021-12-28T12:57:47Z

Same error here

okan-oz · 2022-02-01T07:06:18Z

Same issue with flutter_secure_storage: 4.2.0

fakfa19 · 2022-02-14T17:19:57Z

Still same issue with flutter_secure_storage: 4.2.1

Nazarii77 · 2022-02-22T12:13:12Z

Still same issue with flutter_secure_storage: 5.0.2 (but happens only on some real devices, never on emulator )

loonix · 2022-02-22T15:40:11Z

Have you checked if you are reading a value that does not exist?

AG-IT-Solutions · 2022-03-07T12:19:02Z

Having the same Problem with 5.0.2 and i am, too, trying to read a key that doesn't exist yet. Is there a way to check first if the key exists or not? Tried it with try catch first, which worked, then tried by adding

android:allowBackup="false"
android:fullBackupContent="false"

in AndroidManifest.xml, which fixed the issue, too.

romankis95 · 2022-04-13T10:01:40Z

This line caused the error to me
String value = await _storage?.read(key: "username"); --> version 4.2.0

FreedomLiberty1776 · 2022-05-23T09:57:35Z

I had the same problem with version ^4.2.1 and ^5.0.2 on Samsung J737A which didn't use to happen for a while until I upgraded all my packages. I realized the problem was caused by reading keys that did not yet exist. I solved it by use a simply try catch, and returned null on error, (I think null is the default return value when a key is not found anyways).

static Future getToken() async {
try {
return await _storage.read(key: 'token');
} catch (e) {
return null;
}
}

jfahrenkrug · 2022-06-29T18:52:21Z

If you use version 5.0.2 or newer, make sure you use this option when creating the instance:

FlutterSecureStorage(aOptions: AndroidOptions(
    encryptedSharedPreferences: true,
));

This causes the package to use Android's built-in EncryptedSharedPreferences. The crash only seems to occur when not using this setting, because then the package uses a different way of encrypting and decrypting the prefs. You can see that by reading the source code here:

flutter_secure_storage/flutter_secure_storage/android/src/main/java/com/it_nomads/fluttersecurestorage/FlutterSecureStoragePlugin.java

Line 101 in 26efe91

if (useEncryptedSharedPreferences &&

Also see #328 (comment)

UbaidillahGit · 2023-07-05T14:55:22Z

I used this workaround by adding <application ... android:allowBackup="false" android:fullBackupContent="false">

to AndroidManifest.xml

Thanks it works for me

sajanIocod · 2024-08-08T11:59:03Z

I am still experiencing this issue. Any ideas on how to resolve it?

dukemike mentioned this issue Oct 7, 2020

Storage sometimes returns random data #164

Closed

koskimas mentioned this issue Oct 8, 2020

WRONG_FINAL_BLOCK_LENGTH #163

Closed

timosturm mentioned this issue Apr 22, 2021

PlatformException: BadPaddingException (BAD_DECRYPT in openssl) privacyidea/pi-authenticator#148

Closed

benjaminhorner mentioned this issue Sep 27, 2021

Checking for existing token at app start crashes on certain devices teranetsrl/oauth2_client#99

Closed

juliansteenbakker reopened this Nov 5, 2021

juliansteenbakker mentioned this issue Nov 11, 2021

Android encryption migration #328

Merged

juliansteenbakker closed this as completed in #328 Nov 12, 2021

NamanShergill mentioned this issue Jan 15, 2022

Unhandled Exception: PlatformException(Exception encountered, read, javax.crypto.BadPaddingException: error:1e000065:Cipher functions:OPENSSL_internal:BAD_DECRYPT #354

Open

apidong mentioned this issue Mar 12, 2022

error PlatformException OpenSID/wiki-mobile#20

Closed

dlsagayaraj mentioned this issue May 13, 2022

Error from the dependency flutter_Secure_storage Earlybyte/aad_oauth#150

Closed

PiotrMitkowski mentioned this issue Jul 14, 2022

Android storage fix teranetsrl/oauth2_client#134

Merged

Unhandled Exception: PlatformException(Exception encountered, read, javax.crypto.BadPaddingException: error:1e000065:Cipher functions:OPENSSL_internal:BAD_DECRYPT #161

Unhandled Exception: PlatformException(Exception encountered, read, javax.crypto.BadPaddingException: error:1e000065:Cipher functions:OPENSSL_internal:BAD_DECRYPT #161

Comments

JAICHANGPARK commented Sep 23, 2020

bettdouglas commented Sep 23, 2020

bettdouglas commented Sep 25, 2020

sheychan31 commented Sep 27, 2020

sheychan31 commented Sep 27, 2020

dara1chan commented Sep 28, 2020

HemilTheRebel commented Sep 28, 2020

HemilTheRebel commented Sep 28, 2020

rodrigo-martins-ifood commented Sep 28, 2020 • edited Loading

iNima commented Sep 29, 2020

Andrew-Bekhiet commented Sep 29, 2020

sydneyagcaoili commented Sep 29, 2020

Andrew-Bekhiet commented Sep 29, 2020 • edited Loading

sandeeppatel1986 commented Sep 30, 2020 • edited Loading

iNima commented Sep 30, 2020

mogol commented Sep 30, 2020

HemilTheRebel commented Sep 30, 2020

ldemyanenko commented Oct 5, 2020 • edited Loading

mrevoir commented Oct 5, 2020 • edited Loading

koskimas commented Oct 6, 2020

koskimas commented Oct 6, 2020 • edited Loading

koskimas commented Oct 6, 2020 • edited Loading

koskimas commented Oct 6, 2020 • edited Loading

Tommimon commented Oct 7, 2020

mogol commented Oct 7, 2020

koskimas commented Oct 7, 2020

koskimas commented Oct 8, 2020

mogol commented Oct 8, 2020 via email

Sorunome commented Oct 8, 2020 • edited Loading

postpasspost commented Apr 14, 2021 • edited Loading

komritza commented Jul 6, 2021 • edited Loading

dluanoliveira1 commented Jul 22, 2021 • edited Loading

loonix commented Jul 23, 2021

DineshKachhot commented Aug 20, 2021

appu-sm commented Sep 7, 2021 • edited Loading

romreed commented Oct 15, 2021

rsmaximiliano commented Oct 24, 2021

matthewrice345 commented Nov 4, 2021

kjawadDeveloper2 commented Nov 12, 2021

jesusmartinezd commented Dec 28, 2021

okan-oz commented Feb 1, 2022

fakfa19 commented Feb 14, 2022

Nazarii77 commented Feb 22, 2022

loonix commented Feb 22, 2022

AG-IT-Solutions commented Mar 7, 2022 • edited Loading

romankis95 commented Apr 13, 2022

FreedomLiberty1776 commented May 23, 2022

jfahrenkrug commented Jun 29, 2022

UbaidillahGit commented Jul 5, 2023

sajanIocod commented Aug 8, 2024

rodrigo-martins-ifood commented Sep 28, 2020 •

edited

Loading

Andrew-Bekhiet commented Sep 29, 2020 •

edited

Loading

sandeeppatel1986 commented Sep 30, 2020 •

edited

Loading

ldemyanenko commented Oct 5, 2020 •

edited

Loading

mrevoir commented Oct 5, 2020 •

edited

Loading

koskimas commented Oct 6, 2020 •

edited

Loading

koskimas commented Oct 6, 2020 •

edited

Loading

koskimas commented Oct 6, 2020 •

edited

Loading

Sorunome commented Oct 8, 2020 •

edited

Loading

postpasspost commented Apr 14, 2021 •

edited

Loading

komritza commented Jul 6, 2021 •

edited

Loading

dluanoliveira1 commented Jul 22, 2021 •

edited

Loading

appu-sm commented Sep 7, 2021 •

edited

Loading

AG-IT-Solutions commented Mar 7, 2022 •

edited

Loading