fix: Ajustando whatsapp.bailey.service.ts para mostrar corretamente o…

[jpavrdev]

O conteúdo deste PR já foi aplicado no develop upstream. Os dois commits do fork (4b802391 fix QR Code + a75cdf2c sourcery safe-access) e o fix do isInitialConnection duplicado que eu apliquei no fork também já têm equivalente em develop.

Verificação:

git fetch upstream develop
git rebase upstream/develop
# 4 commits skipped com nota "patch contents already upstream"
# 2 commits restantes dropados com "patch contents already upstream"

git rev-parse HEAD upstream/develop
# 3fb04ed6c39649bee0c448cb5f6d80a0ab269535
# 3fb04ed6c39649bee0c448cb5f6d80a0ab269535

Fechando. Vou resetar o main do meu fork para upstream/develop em seguida.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adjusts WhatsApp Baileys disconnect handling to avoid an infinite reconnect loop during the initial connection phase so the QR code can be displayed correctly.

Sequence diagram for updated WhatsApp Baileys disconnect and reconnect flow

sequenceDiagram
  actor User
  participant WebApp
  participant BaileysStartupService
  participant WhatsAppServer

  User->>WebApp: Open_whatsapp_connection_screen
  WebApp->>BaileysStartupService: connectToWhatsapp(phoneNumber)
  BaileysStartupService->>WhatsAppServer: initiate_connection
  WhatsAppServer-->>BaileysStartupService: connection_update(qr_generated)
  BaileysStartupService-->>WebApp: emit_qrcode(qrcode)
  WebApp-->>User: display_qrcode

  rect rgb(230,230,250)
    WhatsAppServer-->>BaileysStartupService: connection_closed(lastDisconnect)
    BaileysStartupService->>BaileysStartupService: determine_statusCode
    BaileysStartupService->>BaileysStartupService: isInitialConnection = !instance.wuid && instance.qrcode.count == 0

    alt initial_connection_and_qr_not_used_yet
      BaileysStartupService->>BaileysStartupService: log Initial_connection_closed_wait_for_qr
      BaileysStartupService-->>WhatsAppServer: no_reconnect
    else subsequent_disconnect_and_shouldReconnect
      BaileysStartupService->>BaileysStartupService: shouldReconnect = !codesToNotReconnect.includes(statusCode)
      BaileysStartupService->>WhatsAppServer: reconnect_if_shouldReconnect
    else disconnect_with_forbidden_or_logged_out
      BaileysStartupService->>BaileysStartupService: stop_reconnect
    end
  end

Loading

File-Level Changes

Change	Details	Files
Guard the disconnect handler to avoid reconnecting on the very first connection attempt before a QR code is generated.	Compute an isInitialConnection flag based on the absence of wuid and zero QR code generation count. Short‑circuit the disconnect handler when isInitialConnection is true, logging a message and skipping reconnection. Preserve existing behavior for shouldReconnect logic and subsequent reconnection handling when not in the initial connection state.	src/api/integrations/channel/whatsapp/whatsapp.baileys.service.ts

Possibly linked issues

• #: PR adjusts Baileys reconnection/initial connection logic to ensure the QR Code appears, addressing the reported issue

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `src/api/integrations/channel/whatsapp/whatsapp.baileys.service.ts:432` </location>
<code_context>
       const shouldReconnect = !codesToNotReconnect.includes(statusCode);
+
+      // Check if this is the initial connection before QR code generation
+      const isInitialConnection = !this.instance.wuid && this.instance.qrcode.count === 0;
+
+      if (isInitialConnection) {
</code_context>

<issue_to_address>
**issue (bug_risk):** Guard against `this.instance.qrcode` being undefined before accessing `.count`.

If `qrcode` isn’t initialized when disconnect runs, this will throw at runtime. Consider a defensive access pattern (e.g. `this.instance.qrcode?.count ?? 0`) so this remains safe during unusual initialization or disconnect sequences.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[DavidsonGomes]

Hi! Quick request before we can merge — this PR's source branch is your fork's main, which causes two problems:

1. CI workflows don't trigger reliably on fork main branches
2. Future syncs of your fork with upstream become messy

Could you please:

1. Create a new branch from your current commits (e.g. git checkout -b feat/<short-name>)
2. Reset your fork's main to upstream's main/develop
3. Update this PR's head branch (or close this and open a new PR from the new branch)

Base branch should target develop. Once CI runs green I'll re-review. Thanks!

[jpavrdev]

Fechando — obsolete (já aplicado em develop). Ver body atualizado.