Chrome Driver issue(Mac) - sbase install chromedriver 110' returned non-zero exit status 1. #1741
              
                
                  
                  
                    Answered
                  
                  by
                    mdmintz
                  
              
          
                  
                    
                      abdurraheemj
                    
                  
                
                  asked this question in
                Q&A
              
            -
Beta Was this translation helpful? Give feedback.
      
      
          Answered by
          
            mdmintz
          
      
      
        Feb 9, 2023 
      
    
    Replies: 2 comments
-
| Hello, the Chromium Team recently changed how they packed drivers. More info here: #1663 | 
Beta Was this translation helpful? Give feedback.
                  
                    0 replies
                  
                
            
      Answer selected by
        mdmintz
-
| Thanks Michael, problem solved On Wed, Feb 8, 2023 at 6:49 PM Michael Mintz ***@***.***> wrote:
 Hello, the Chromium Team recently changed how they packed drivers.
 Upgrading to the latest version of SeleniumBase should fix your issue.
 More info here: #1663
 <#1663>
 —
 Reply to this email directly, view it on GitHub
 <#1741 (comment)>,
 or unsubscribe
 <https://github.com/notifications/unsubscribe-auth/AQTL6TGIMV23FMUFR4YGPETWWQ5JDANCNFSM6AAAAAAUV5NMXQ>
 .
 You are receiving this because you authored the thread.Message ID:
 ***@***.***
 com>
 -- 
*Thanks & Regards,*
Raheem Jameel
Software QA Engineer
Apartment Home Living - CoStar Group
https://www.apartmenthomeliving.com
Contact : (510)586-2375 | 
Beta Was this translation helpful? Give feedback.
                  
                    0 replies
                  
                
            
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Hello, the Chromium Team recently changed how they packed drivers.
Upgrading to the latest version of SeleniumBase should fix your issue.
More info here: #1663