Unsolved Warning: Trying to access array offset on value of type null when trying to refresh a mailbox

[escozul]

@peopleinside
Hello
in my .env, I see the following:

###> symfony/framework-bundle ###
APP_ENV=dev
APP_SECRET=YOUR_APP_SECRET

Is that correct? Should I have set the app secret somewhere? ... or it does not matter?

My uvdesk.yaml:

parameters:
    app_locales: en|fr|it|de|da|ar|es|tr|zh|pl
    
    # Default Assets
    assets_default_agent_profile_image_path: 'bundles/uvdeskcoreframework/images/uv-avatar-batman.png'
    assets_default_customer_profile_image_path: 'bundles/uvdeskcoreframework/images/uv-avatar-ironman.png'
    assets_default_helpdesk_profile_image_path: 'bundles/uvdeskcoreframework/images/uv-avatar-uvdesk.png'

    uvdesk_site_path.member_prefix: --------- #Masked for security
    uvdesk_site_path.knowledgebase_customer_prefix: --------- #Masked for security
    
    # File uploads constraints
    # @TODO: Set these parameters via compilers
    max_post_size: 8388608
    max_file_uploads: 20
    upload_max_filesize: 2097152

uvdesk:
    site_url: 'helpdes.mydomain.com' # No /public here. It's properly set.
    upload_manager:
        id: Webkul\UVDesk\CoreFrameworkBundle\FileSystem\UploadManagers\Localhost
    
    support_email:
        id: email@mydomain.com #properly set to my domain. Changed it for security purposes
        name: Support HelpDesk
        mailer_id: mailer_SES
    
    # Default resources
    default:
        ticket:
            type: support
            status: open
            priority: low
        templates:
            email: mail.html.twig

Tried to mask some. Sorry for that. They seem just fine though.

Edit:

I visited the address found here: API https://uvdesk.example.com/mailbox/listener
kept bugging me.

The result on screen was:
{"success":false,"message":"Request not supported."}
Have no idea what that is! what is it?
What about the API? When I go over to settings, the first selection is the API:

I haven't used that access token anywhere. What's it for? Should I put it in the .env file?

[peopleinside]

@escozul

Could you try to replace the

site_url: 'helpdes.mydomain.com' # No /public here. It's properly set.

with

site_url: helpdes.mydomain.com

Then clean cache php bin/console c:c and try to fetch email again. Still facing the issue?

[escozul]

@peopleinside

Thank you. Same error though.

[peopleinside]

@escozul I have no others idea sorry.

All thread suggested where user are solved seems are not helping you, from what you said. I don't know what else suggest.

Usually from what I see the error can be caused by a wrong domain settings, from some server settings like HTTP and not HTTPS, there are also some fix suggested in other topics.

I'm currently not facing this issue on my active installation.
I'm sorry to see we was not able to resolve.

[escozul]

@peopleinside
Thank you for your time.
I appreciate all your help.

Well.. Let's hope that in the following days, someone will come across this issue and help me resolve it.

[peopleinside]

@escozul I wish you to resolve

[leooxx]

Hello,

To fix this error, you must install the php extension "maileparse"

Apt debian command : sudo apt install php8.1-mailparse

The full error message is in the log app :

{"message":"Uncaught Error: Call to undefined function PhpMimeMailParser\\mailparse_msg_create()","context":{"exception":{"class":"Error","message":"Call to undefined function PhpMimeMailParser\\mailparse_msg_create()","code":0,"file":"/web/www/uvdesk/vendor/php-mime-mail-parser/php-mime-mail-parser/src/Parser.php:195"}},"level":500,"level_name":"CRITICAL","channel":"php","datetime":"2024-03-24T16:40:04.785031+01:00","extra":{}}

[escozul]

@leooxx Thank you.

Will try that on Tuesday and get back here to post if it's resolved or not.

[escozul]

@leooxx Hello,
I can't find that entry on any of my logs. How do you know that the error is with the php-mailparse addon?

cause running PHP -m lists mailparse right there..

You mentioned a "logs app"... Can't find that.

[peopleinside]

@escozul

usually when I was using UVdesk for check if the mail parse was present and detected by UVdesk I use to generate a new UVdesk instance and run the setup wizard.

The UVdesk setup wizard show you if you have all requirements.
I suggested, since long time to the UVdesk team to add a health page that help already present installation to be checked but since different months now UVdesk seems abandoned in the open source project.

I migrated to a different solution and left also the forum also if I still get an eye here sometimes

[escozul]

@peopleinside Hello,

Did you migrate to a different solution? Do you mind sharing it?

[peopleinside]

@escozul currently I'm using freescout that is not all completely free but seems fine is updated and works quite well. I'm very sad to have to leave UVdesk but I had some serous bug with attachments for example that was not fixed and I did not see updates so decided to migrate.

Currently we dont know if UVdesk open source will be supported in the future, loooks strange to me support for the open source has been frozen for mounts and seems also the development on GitHub is frozen.

[escozul]

@peopleinside Than you for replying. Freescout seems free... Maybe the modules are paid but the core seems free. UVdesk plugins are also paid for so I guess it's kind of the same...

That's a nice alternative. Since it's self-hosted, I might give it a go!

[peopleinside]

@escozul correct. With the base you have very basilar function you miss workflow, user interface, etc... so at the end it's easy you will need buy something. but you can see the online full demo