If PullDownMenuItem's onTap is a showDialog function, nothing happens when clicking it.

[LathDevers]

PullDownButton(
        itemBuilder: (ctx) => [
          PullDownMenuItem(
            title: 'Compress',
            icon: CupertinoIcons.archivebox,
            onTap: () => showDialog(context: context, builder: (context) => AlertDialog(content: Container())),
          ),
        ],
        position: PullDownMenuPosition.under,
        buttonBuilder: (context, showMenu) => CupertinoButton(
          onPressed: showMenu,
          padding: EdgeInsets.zero,
          child: Icon(CupertinoIcons.ellipsis_circle),
        ),
      ),

[notDmDrl]

Hi @LathDevers, thanks for submitting issue

I am able to reproduce this issue with PullDownButton as well as with PopupMenuButton, so I'd say this behaviour is expected.

Both of menu buttons first call a onTap function and then immediately fire Navigator.pop(), which in this case show and immediately hide dialog as well as not pop menu since navigation stack was changed. Relevant stackoverflow issue

As a working solution, while not perfect, consider this:

PullDownButton(
  itemBuilder: (ctx) => [
    PullDownMenuItem(
      title: 'Compress',
      icon: CupertinoIcons.archivebox,
      onTap: () async {
        await Future<void>.delayed(const Duration(milliseconds: 1));
        await showDialog<void>(
          context: context,
          builder: (context) => AlertDialog(content: Container()),
        );
      },
    ),
  ],
  position: PullDownMenuPosition.under,
  buttonBuilder: (context, showMenu) => CupertinoButton(
    onPressed: showMenu,
    padding: EdgeInsets.zero,
    child: const Icon(CupertinoIcons.ellipsis_circle),
  ),
)

Although I will try to come up with a better solution in a couple of weeks when I have more time (or at least update examples/documentation with example that i provided).

[LathDevers]

Hi @LathDevers, thanks for submitting issue

I am able to reproduce this issue with PullDownButton as well as with PopupMenuButton, so I'd say this behaviour is expected.

Both of menu buttons first call a onTap function and then immediately fire Navigator.pop(), which in this case show and immediately hide dialog as well as not pop menu since navigation was stack changed. Relevant stackoverflow issue

As a working solution, while not perfect, consider this:

PullDownButton(
  itemBuilder: (ctx) => [
    PullDownMenuItem(
      title: 'Compress',
      icon: CupertinoIcons.archivebox,
      onTap: () async {
        await Future<void>.delayed(const Duration(milliseconds: 1));
        await showDialog<void>(
          context: context,
          builder: (context) => AlertDialog(content: Container()),
        );
      },
    ),
  ],
  position: PullDownMenuPosition.under,
  buttonBuilder: (context, showMenu) => CupertinoButton(
    onPressed: showMenu,
    padding: EdgeInsets.zero,
    child: const Icon(CupertinoIcons.ellipsis_circle),
  ),
)

Although I will try to come up with a better solution in a couple of weeks when I have more time (or at least update examples/documentation with example that i provided).

Thanks, that's a perfectly fine workaround for now. 😉

[rikbrown]

The above workaround works for me with a CupertinoAlertDialog too, thanks!

[notDmDrl]

@LathDevers, @rikbrown,

I have just published an update which should have fixed this issue (at least from my testing it did).

Now its pretty straightforward, just remove await Future<void>.delayed(const Duration(milliseconds: 1)):

PullDownButton(
  itemBuilder: (ctx) => [
    PullDownMenuItem(
      title: 'Compress',
      icon: CupertinoIcons.archivebox,
      onTap: () => showDialog<void>(
        context: context,
        builder: (context) => AlertDialog(content: Container()),
      ),
    ),
  ],
  position: PullDownMenuPosition.under,
  buttonBuilder: (context, showMenu) => CupertinoButton(
    onPressed: showMenu,
    padding: EdgeInsets.zero,
    child: const Icon(CupertinoIcons.ellipsis_circle),
  ),
)

[LathDevers]

I have just published an update which should have fixed this issue (at least from my testing it did).

...

@notDmDrl thanks! It works for me now 👍🏻
Tested on Android 12 (physical device) and iOS 15.5 (simulator and physical device)