You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm not an expert here (so I'm probably missing something) but I was recently trying to debug a custom Fastlane lane with rdbg using vscode with the following terminal command:
But it seems that the editor cannot load the source file: the Fastfile (see attached screenshot). I would guess that some context information are not correctly passed to the editor (am I missing some parameters?).
If I debug from the terminal, using the following command:
rdbg -c -- bundle exec fastlane custom_lane
Everything seems to work correctly (see attached screenshot).
I prepared an example repo to easily reproduce the issue.
Thanks in advance for your support, and sorry if it's a stupid question 😅
Your environment
ruby -v
:ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [arm64-darwin23]
rdbg -v
:rdbg 1.9.1
Describe the bug
I'm not an expert here (so I'm probably missing something) but I was recently trying to debug a custom Fastlane lane with
rdbg
usingvscode
with the following terminal command:rdbg --open=vscode -c -- bundle exec fastlane custom_lane
But it seems that the editor cannot load the source file: the
Fastfile
(see attached screenshot). I would guess that some context information are not correctly passed to the editor (am I missing some parameters?).If I debug from the terminal, using the following command:
rdbg -c -- bundle exec fastlane custom_lane
Everything seems to work correctly (see attached screenshot).
I prepared an example repo to easily reproduce the issue.
Thanks in advance for your support, and sorry if it's a stupid question 😅
To Reproduce
bundle install
rdbg -c -- bundle exec fastlane custom_lane
vscode
with:rdbg --open=vscode -c -- bundle exec fastlane custom_lane
Expected behavior
I would expect to debug the
custom_lane
similarly from both terminal andvscode
.The text was updated successfully, but these errors were encountered: