Stuck on Channel 1 created

[Drjacky]

Steps to reproduce

How'd you do it?

1. Get meterpreter session
2. Run shell command

Expected behavior

Access device shell

Current behavior

Stuck on Channel 1 created

Metasploit version

metasploit v6.3.42-dev-5b888c49cb022a2c532d1e4296e93c614c211cba

Android 9

[github-actions]

It looks like there's not enough information to replicate this issue. Please provide any relevant output and logs which may be useful in diagnosing the issue.

This includes:

• All of the item points within this template
• The result of the debug command in your Metasploit console
• Screenshots showing the issues you're having
• Exact replication steps

The easier it is for us to replicate and debug an issue means there's a higher chance of this issue being resolved.

[github-actions]

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

[Drjacky]

[timwr]

@Drjacky this is working as expected, try typing a command.

I suggest we:

1. Remove the channel/process logging
2. Default to a pty shell on compatible meterpreters?

[timwr]

For 1. maybe we can sneak this change in without @wvu noticing: #11982

[github-actions]

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

[github-actions]

Hi again!

It’s been 60 days since anything happened on this issue, so we are going to close it.
Please keep in mind that I’m only a robot, so if I’ve closed this issue in error please feel free to reopen this issue or create a new one if you need anything else.

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.