RemoteAuth saving an increasingly large file becoming unmaintainable in a short time

[GuilhermeRX]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

The zip file generated by RemoteAuth has become increasingly larger, so that it becomes unsustainable in a short time, as I will have huge costs for data traffic in the clouds. I don't know what to do to solve the problem. Can anyone help me

Expected behavior

The remote authentication zip file should never exceed 50MB

Steps to Reproduce the Bug or Issue

const store = new AwsS3Store({
bucketName: 'xxxxx',
remoteDataPath: 'xxxxxxxx',
s3Client: s3,
putObjectCommand,
headObjectCommand,
getObjectCommand,
deleteObjectCommand
});

const hours = +process.env.BACKUP_HOURS;
const backupMsTime = hours * 60 * 60 * 1000;

const remoteAuth = new RemoteAuth({
clientId: 'client_id',
dataPath: 'path_here',
store: store,
backupSyncIntervalMs: backupMsTime
});

const client = new Client({
authStrategy: remoteAuth,
puppeteer: {
executablePath: '/usr/bin/chromium-browser',
args: [
"--no-sandbox",
"--disable-setuid-sandbox",
],
headless: true,
},
});

Relevant Code

No response

Browser Type

Chromium

WhatsApp Account Type

Standard

Does your WhatsApp account have multidevice enabled?

No, I am not using Multi Device

Environment

OS: [ Linux, Docker + node-alpine]
Phone OS: [e.g. Android, iOS]
whatsapp-web.js version [1.25.0]
Node.js Version [20.14]

Additional context

No response

[williamsouto-dev]

Any solution to this problem? My storage is almost 2GB

[GuilhermeRX]

Any solution to this problem? My storage is almost 2GB

I still don't have a solution for this problem, I'm seriously considering disabling remote authentication. Furthermore, now the code recovers the session and simply hangs, does not generate a new qr code and also does not complete the login

[AKwoKWH]

I guess it is the same thing
#3222