search

microsoft / botbuilder-python

The Microsoft Bot Framework provides what you need to build and connect intelligent bots that interact naturally wherever your users are talking, from text/sms to Skype, Slack, Office 365 mail and other popular services.
http://botframework.com
MIT License
717 stars 286 forks source link

Version solving failed/Dependency error #1924

Closed ekouidinov closed 2 years ago

ekouidinov commented 2 years ago

Version

4.14.1

Describe the bug

Botbuilder is not compatible with msal version >1.6.0 since botframework-connector depends on msal 1.6.0

To Reproduce

Steps to reproduce the behavior:

  1. Open linux terminal
  2. cd /tmp && mkdir bot && cd bot
  3. poetry init
  4. Fill in poetry project info
  5. poetry add msal
  6. poetry add botbuilder-core
  7. See the error

Expected behavior

Complete installation

Screenshots

Using version ^4.14.1 for botbuilder-core

Updating dependencies
Resolving dependencies... (0.7s)

  SolverProblemError

  Because no versions of botbuilder-core match >4.14.1,<5.0.0
   and botbuilder-core (4.14.1) depends on botframework-connector (4.14.1), botbuilder-core (>=4.14.1,<5.0.0) requires botframework-connector (4.14.1).
  And because botframework-connector (4.14.1) depends on msal (1.6.0), botbuilder-core (>=4.14.1,<5.0.0) requires msal (1.6.0).
  So, because msteams-bot depends on both msal (^1.17.0) and botbuilder-core (^4.14.1), version solving failed.

Additional context

I don't have an option to downgrade msal because I need to use >=1.7.0 version in my project

anishprasad01 commented 2 years ago

Hello @ekouidinov,

You are correct that this version of MSAL is not currently supported. Unfortunately, at this time we do not have a workaround for you since you have already specified that downgrading packages is not an option.

I can tell you that MSAL support is actively being worked on, however we do not have an ETA at this time for when this feature will be available.

FionnD commented 2 years ago

I know this issue is closed, but leaving this message to highlight this is still an issue! and is there an updated ETA?