Jon Erickson

That is the whole purpose of Community Hive! Every interaction with it intends to drive customer/clients/users BACK to your community. It does not want to be the center of attention!

That is the whole purpose of Community Hive! Every interaction with it intends to drive customer/clients/users BACK to your community. It does not want to be the center of attention!

I’ve tried both and messed around with several different flows. This is the fastest way for me. It aligns with other industry standards for project development as well and I can spin up a dev environment in a few key strokes. Not to mention I’ll configure it to the dev container spec as well so it can be used in any dev environment including remote. 

Myr... that only works if you're using AWS for sending email.  It is basically the same thing for @Jon Erickson's app as well.  (Which is what I used for a long time and works great.)
With that said... that would mean to do this, IPS would have to dictate that customers would have to use AWS for sending email.  The vast majority of self-hosted customers are not using it and would be hard-pressed to properly setup SES, configure SNS notifications, get out of the AWS sandbox, create the correct DNS/DKIM/SPF record, etc.   
Can you imagine the amount of support and hand holding that would need to be done?  I'm a fairly competent system admin, and I still had a complication or two that Jon had to help me with.  Imagine the normal customer who does not understand setting up IAM roles and the difference between SNS and SES.  It becomes a train wreck before it's even had a chance to leave the station.  🙂 

Yes.  I have created new user. Screen seems changed because I google and other tutorials had different screen as well. 
Thanks for quick response. I will ask next step if I get stuck anywhere. - Thank you.
 

I had something similar happen with one of my other applications and it boiled down to composer issues - which as you can see throughout this forum, I think they are still trying to iron out how they manage their dependencies while allowing 3rd party devs to include their dependencies.

AWS: 3.235.14
Guzzle: 7.5.0
Yeah, no problem. Looks like I need to examine another function argument. No problem. Will update soon. 

Gotcha. Thanks for the insight. 

Gotcha. Thanks for the insight. 

Actually, I think we're good - we were using smtp credentials rather than the correct user key etc. Seems ok now, I think. 

Hmm interesting. Will look into. Thanks for posting. 

Have you confirmed your cron is running with PHP 7.4+? Most web hosting providers allow you to configure cron PHP version independently of your website PHP version. Sounds like your cron is executed using an old PHP version. 

Experienced it as well. 

Correct. That’s why I had him use my fix which just included sources/vendor to allow the rest of the sources folder to still be included. 

Just an update here.. sources/vendor will be excluded from the Scanner in the November release!
This is a bad approach because it's literally going to exclude everything from the sources directory which means any own Item,Comment,etc class which extends one of the base IPS classes wouldn't be checked.

I appreciate @Randy Calvert responses. They are exactly what I would have said. 
With that being said, we will await IPS’ response on where to place the vendor folder. It is currently in the sources folder as I was directed by @Daniel F to do so. I originally had it in the root application directory when I first released the application but it sounds like that wasn’t kosher.

I appreciate @Randy Calvert responses. They are exactly what I would have said. 
With that being said, we will await IPS’ response on where to place the vendor folder. It is currently in the sources folder as I was directed by @Daniel F to do so. I originally had it in the root application directory when I first released the application but it sounds like that wasn’t kosher.

Check my previous post for the update to fix it. 

Looks like it was shipped with 4.7.3. Line 78 of Scanner.php:
$excludeDirs = [ 'hooks', 'setup', 'dev', 'vendor' ]; HOWEVER, the patch, as it stands right now, will not work as the regex pattern is looking for a directory path of
/\/var\/www\/html\/applications\/awsses\/(?:hooks|setup|dev|vendor)/
The vendor folder is located in the sources directory as required by IPS, not the root application folder.
@Daniel F, do I move my vendor folder to the root directory or do you guys update the regex to look for the vendor folder in the sources directory? 
For the time being, you can edit line 78 of Scanner.php to the following to fix the issue.
$excludeDirs = [ 'hooks', 'setup', 'dev', 'vendor', 'sources\/vendor' ];

yes it is working on my test site.
Now PHP8 does not work but this is another matter.

Thanks for the support. 

I finally recreated the issue in my local environment and received the following stack trace. Confirmed it is indeed attributed to the compatibility scanner and trying to scan the entire vendor/dependency folder.
# Time Memory Function Location 1 0.0014 406056 {main}( ) .../index.php:0 2 0.1819 9685824 IPS\_Dispatcher->run( ) .../index.php:13 3 0.1820 9687328 IPS\core\modules\admin\support\_support->execute( ) .../Dispatcher.php:153 4 0.1820 9687328 IPS\Dispatcher\_Controller->execute( ) .../support.php:48 5 0.1820 9687328 IPS\core\modules\admin\support\_support->getBlock( ) .../Controller.php:107 6 0.1820 9687376 IPS\core\modules\admin\support\_support->_showBlockHookscanner( ) .../support.php:228 7 0.1845 9851896 IPS\Application\_Scanner::scanCustomizationIssues( $getDetails = FALSE, $shallowCheck = TRUE, $limit = 500, $options = ['shallowCheckEnabledOnly' => TRUE, 'enabledOnly' => FALSE] ) .../support.php:519 8 0.1983 9938336 IPS\Application\_Scanner::scanExtendedClasses( $getDetails = FALSE, $shallowCheck = TRUE, $limit = 500, $hardLimit = 5000, $options = ['shallowCheckEnabledOnly' => TRUE, 'enabledOnly' => FALSE] ) .../Scanner.php:786 9 21.4599 13207736 IPS\Application\_Scanner::getClassDetails( $scriptContents = '<?php\n// This file was auto-generated from sdk-root/src/data/apigateway/2015-07-09/api-2.json\nreturn [ \'version\' => \'2.0\', \'metadata\' => [ \'apiVersion\' => \'2015-07-09\', \'endpointPrefix\' => \'apigateway\', \'protocol\' => \'rest-json\', \'serviceFullName\' => \'Amazon API Gateway\', \'serviceId\' => \'API Gateway\', \'signatureVersion\' => \'v4\', \'uid\' => \'apigateway-2015-07-09\', ], \'operations\' => [ \'CreateApiKey\' => [ \'name\' => \'CreateApiKey\', \'http\' => [ \'method\' => \'POST\', \'requestUri\' => \'/apikeys\', \'responseCode\' => 20'... ) .../Scanner.php:175 Running into a max execution time. 

more info here : 
 
 
On my sever i end up with script timeout on scanner.php. Renaming the app folder solved the issue instantly (but the app probably does not work).

From what I can see from the logs, it is trying to look for files/directories in the vendor folder and it is receiving a not found error. This vendor folder contains all the crucial dependencies needed to run the application. I have double-checked the bundle to make sure the files are present and they are. Can you check your server and see if the files that are named in the log file you provided are indeed present?
Example:
/home/******/public_html/applications/awsses/sources/vendor/aws/aws-sdk-php/  

To close the loop on this...  the new version hit marketplace a little bit ago.  I was able to install it without errors on PHP 8.0.20.  Confirmed that email is still delivering as well.