Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

PusherEvent push data in fragment twice

未关闭
#272 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
半天
新手友好度
22/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
android, java
领域
mobile, networking

调研方向

The report is a user question about a Pusher client snippet inside an Android Fragment, not a described code change, and it has been silent for about six years. Start by checking whether connect(), subscribe() and bind() run more than once per event, for example on every onCreateView or onResume, and whether the earlier listener is ever unbound. Done would mean a reproduction that explains the duplicate log line, plus a maintainer or reporter confirmation of the cause.

由索引模型根据 Issue 内容生成。

描述

question

Below here my code inside fragment:

`options = new PusherOptions();
options.setCluster(cluster_pusher);

    pusher = new Pusher(key_pusher, options);

    pusher.connect(new ConnectionEventListener() {
        @Override
        public void onConnectionStateChange(ConnectionStateChange change) {
            Log.i("Pusher", "State changed from " + change.getPreviousState() +
                    " to " + change.getCurrentState());
        }

        @Override
        public void onError(String message, String code, Exception e) {
            Log.i("Pusher", "There was a problem connecting! " +
                    "\ncode: " + code +
                    "\nmessage: " + message +
                    "\nException: " + e
            );
        }
    }, ConnectionState.ALL);

    channel = pusher.subscribe(Config.TOPIC_GLOBAL);
    
      channel.bind(Config.PUSHER_EVENT, new SubscriptionEventListener() {
        @Override
        public void onEvent(PusherEvent event) {
            Log.i("Pusher", "Received event with data: " + event.getData());

}
});`

why?

主要语言
Java
星标
315
派生
140
平均合并
11 天 5 小时
30 天内合并 PR
4

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

pusher/pusher-websocket-java 的其他 Issue

查看 pusher/pusher-websocket-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。