Skip to content

The Arduino Cloud Agent 1.6.1 will not update the certificate in Safari 18.3.1 #1034

Open
@EETechFix

Description

@EETechFix

Describe the problem

The Arduino Cloud Agent 1.6.1 appears to be incompatible with Safari 18.3.1 or 18.2. I had the same problem on two different Mac computers. When attempting to add a device to the cloud, I encounter the Setup Device page, as it’s not recognizing the board despite having Cloud Rev 1.6.1 installed and running. The Agent will not let me update the certificate in Safari; I get the same read error: -61. When I tried to add a device to the cloud with Chrome or Firefox, it worked fine. I’m running macOS Sequoia 15.3.2.

This is the result of the Investigate macOS Permissions ~/.arduino-create step. The .arduino-create folder (a hidden folder/file) appears at the location where the read error occurs; details are listed below.

CONSOLE LOG:
error 01:40:21.328356-0700 kernel Sandbox: ecosystemanalyticsd(612) deny(1) file-read-data /Users/slysam/.arduino-create/builtin/serial-discovery/1.4.1
error 01:40:21.328474-0700 kernel Sandbox: ecosystemanalyticsd(612) deny(1) file-read-data /Users/slysam/.arduino-create/builtin/serial-discovery/1.4.1/serial-discovery

To reproduce

Safari 18.3.1: Try adding an Arduino Uno R4 to the cloud; it will not recognize the board or any other cloud-compatible board, despite having the Arduino Cloud Agent Rev 1.6.1 installed and running.

Try updating the certificate in Safari using my system, which returns read error -61

Expected behavior

Safari 18.3.1: Try adding an Arduino Uno R4 to the cloud; it will not recognize the board or any other cloud-compatible board, despite having the Arduino Cloud Agent Rev 1.6.1 installed and running.

Try updating the certificate in Safari using my system, which returns read error -61

Arduino Create Agent version

Arduino Cloud Agent 1.6.1

Operating system

macOS

Operating system version

15.3.2

Browser

Safari 18.3.1

Browser version

Safari 18.3.1

Additional context

No response

Issue checklist

  • I searched for previous reports in the issue tracker
  • I verified the problem still occurs when using the latest version
  • My report contains all necessary details

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: imperfectionPerceived defect in any part of project

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions