‹ Reports
The Dispatch

Telegram iOS Project Faces Persistent Media Handling Bugs Amid Ongoing Development Efforts

The Telegram iOS project, the official repository for the Telegram messaging app on iOS, continues to experience high levels of development activity. The project aims to provide a robust messaging platform with a focus on user privacy and security.

Recent activities have highlighted persistent issues with media handling, particularly video playback and image processing. Users report problems such as videos in incorrect formats not playing correctly and issues with image quality. These media-related bugs are a recurring theme in recent issues, indicating an area needing focused attention. Despite these challenges, the development team has been actively working on enhancing features related to user engagement, such as star functionalities.

Recent Activity

Recent issues and pull requests (PRs) indicate a focus on both bug fixes and feature enhancements. Media handling bugs dominate the issues list, with users reporting problems like video lag (#1508) and inability to dismiss full-screen videos (#1506). There is also frustration over unresolved long-standing issues, such as call audio problems post-alarm (#1496).

Development Team and Recent Activity

Isaac

Ilya Laktyushin (laktyushin)

Mike (overtake)

Of Note

  1. Media Handling Bugs: Persistent issues with video playback and image processing suggest a need for targeted bug fixes.
  2. Collaborative Development: Strong collaboration between Isaac and Ilya on feature development, particularly around user engagement features.
  3. Localization Efforts: Continuous updates to localization files highlight an emphasis on internationalization.
  4. Contributor Challenges: Multiple open PRs with limited recent activity suggest potential bottlenecks in the review process.
  5. Security Emphasis: Ongoing attention to security-related PRs underscores the project's commitment to user privacy.

Quantified Reports

Quantify Issues



Recent GitHub Issues Activity

Timespan Opened Closed Comments Labeled Milestones
7 Days 10 4 1 4 1
30 Days 43 19 27 11 1
90 Days 92 56 63 23 1
1 Year 278 181 320 77 1
All Time 1324 854 - - -

Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.

Quantify commits



Quantified Commit Activity Over 30 Days

Developer Avatar Branches PRs Commits Files Changes
Ilya Laktyushin 1 0/0/0 56 200 10591
Isaac 1 0/0/0 41 152 8287
Mike 1 0/0/0 7 6 148
None (TochkaG) 0 0/0/1 0 0 0
Ertem Biyik (ertembiyik) 0 1/0/0 0 0 0

PRs: created by that dev and opened/merged/closed-unmerged during the period

Detailed Reports

Report On: Fetch issues



Recent Activity Analysis

The Telegram iOS project has seen significant recent activity, with a total of 470 open issues. Among these, several issues have been created or updated in the past few days, indicating ongoing user engagement and the identification of bugs or feature requests. Notably, many issues revolve around bugs related to media handling, user interface inconsistencies, and integration challenges with new iOS features.

A recurring theme in the recent issues is the handling of media files, particularly regarding video playback and image processing. Users are reporting problems such as videos being sent in incorrect formats (e.g., MKV files not playing correctly), issues with image quality when shared, and difficulties in managing media within secret chats. Additionally, there are reports of functional discrepancies when using the app across different devices and operating systems.

Issue Details

Here are some of the most recently created and updated issues:

  1. Issue #1515: Created 1 day ago by halopolicja

    • Priority: N/A
    • Status: Open
    • Description: No details provided.
  2. Issue #1514: Created 2 days ago by davido1022

    • Priority: Bug
    • Status: Open
    • Description: A bug report template was initiated but lacks specific details.
  3. Issue #1512: Created 2 days ago by Satthawut2547

    • Priority: N/A
    • Status: Open
    • Description: A reminder for users to fill out the bug report template properly.
  4. Issue #1509: Created 2 days ago by Janesh suthar

    • Priority: Bug
    • Status: Open
    • Description: Encountered an error while trying to generate an Xcode project after cloning the repository.
  5. Issue #1508: Created 4 days ago by nikalasmd

    • Priority: Bug
    • Status: Open
    • Description: Videos using H.265 codec are lagging during playback within the Telegram app.
  6. Issue #1506: Created 7 days ago by Sebastian Kassai

    • Priority: Bug
    • Status: Open
    • Description: Users are unable to dismiss video files when viewed in full screen.
  7. Issue #1496: Created 9 days ago by Maria Dzhenkova

    • Priority: Bug
    • Status: Open
    • Description: Users cannot hear their partner during a call after an iPhone alarm goes off; this issue has been persistent since 2022.
  8. Issue #1495: Created 9 days ago by Aaron

    • Priority: Bug
    • Status: Open
    • Description: Users report not receiving push notifications despite having APNS certification uploaded.

Important Observations

  • The issues indicate a pattern of ongoing media-related bugs, particularly concerning video playback and sharing functionalities.
  • There is a notable lack of detail in some reports, which could hinder troubleshooting efforts.
  • Several users have expressed frustration over longstanding issues that remain unresolved, suggesting a need for more robust communication from developers regarding bug fixes and updates.

This analysis highlights critical areas where user experience may be impacted due to unresolved bugs and emphasizes the importance of thorough issue reporting for effective resolution.

Report On: Fetch pull requests



Overview

The analysis of the pull requests (PRs) for the Telegram iOS project reveals a total of 30 open PRs, with a significant focus on UI improvements, bug fixes, and feature enhancements. The PRs reflect ongoing development efforts and community engagement, but also highlight issues related to contributor activity and the merging process.

Summary of Pull Requests

Open Pull Requests

  1. PR #1497: Fix ripple effect wave animation

    • State: Open
    • Created: 9 days ago
    • Significance: Addresses a UI bug in ripple effect animations. This PR is crucial for enhancing user experience by ensuring smooth animations.
  2. PR #1186: Contest UI 23

    • State: Open
    • Created: 358 days ago
    • Significance: A work-in-progress (WIP) PR focused on contest UI improvements. It has multiple commits indicating ongoing adjustments but lacks recent activity.
  3. PR #1185: iOS UI Competition 2023

    • State: Open
    • Created: 358 days ago
    • Significance: Another WIP PR aimed at enhancing the UI for a competition. Similar to #1186, it shows extensive work but limited recent updates.
  4. PR #1430: Fix issues #1410 and #1298

    • State: Open
    • Created: 63 days ago
    • Significance: Addresses specific issues within the codebase, reflecting active maintenance efforts.
  5. PR #1424: Add Organic Maps app to the Open in options

    • State: Open
    • Created: 66 days ago
    • Significance: Expands functionality by integrating an additional mapping application, enhancing user options.
  6. PR #1413: Remove 'import ContextUI' duplicates

    • State: Open
    • Created: 77 days ago
    • Significance: A minor cleanup that improves code quality by removing unnecessary imports.
  7. PR #1401: Take playAndRecord permission only when recording (fixes #1209)

    • State: Open
    • Created: 114 days ago
    • Significance: Enhances audio handling during video recording, improving user experience.
  8. PR #1389: Remove unused variables in animations.c

    • State: Open
    • Created: 131 days ago
    • Significance: Code cleanup that optimizes performance by removing unnecessary variables.
  9. PR #1382: Fix conflicting check for Archive Chat context item

    • State: Open
    • Created: 147 days ago
    • Significance: Resolves a logical conflict in the chat context menu, improving functionality.
  10. PR #1344: Fix 2GIS logo

    • State: Open
    • Created: 203 days ago
    • Significance: Addresses a branding issue that affects user perception and app professionalism.

Closed Pull Requests

  • Numerous closed PRs indicate a backlog of contributions that were not merged, with many being minor fixes or enhancements.
  • Notable closed PRs include those addressing security vulnerabilities (e.g., CVE patches) and significant feature additions like support for new applications in the "Open In" menu.

Analysis of Pull Requests

The current landscape of open pull requests for the Telegram iOS project highlights several themes and areas of concern:

Activity Levels and Engagement

The presence of multiple WIP PRs (#1186 and #1185) suggests ongoing community engagement in enhancing the UI and adding features. However, their lack of recent activity raises questions about contributor follow-through or potential bottlenecks in the review process. The community's enthusiasm is evident, yet it appears that many contributions are stalled or awaiting feedback.

Code Quality and Maintenance

Several PRs focus on code cleanup and bug fixes (#1413, #1401, #1389). This indicates a commitment to maintaining code quality alongside feature development. Regular maintenance is essential for long-term project health, especially in a large codebase like Telegram's.

Feature Expansion vs. Bug Fixing

There is a noticeable balance between feature expansion (e.g., integrating new apps into the "Open In" options) and addressing existing bugs (e.g., fixing animation issues). This dual focus is crucial as it ensures that while new functionalities are being added, existing user experiences are not compromised.

Contributor Challenges

The number of closed PRs without merges reflects potential challenges faced by contributors, such as unclear guidelines or slow review processes. For instance, PRs like #1449 remain unmerged due to CLA signing issues or lack of response from maintainers, which could discourage future contributions.

Security and Compliance

The emphasis on security-related PRs indicates an awareness of the importance of safeguarding user data within messaging applications. This is particularly relevant given Telegram's focus on privacy and secure communication.

Conclusion

In summary, while there is robust activity within the Telegram iOS repository, challenges remain regarding contributor engagement and the merging process for pull requests. Addressing these issues could enhance community involvement and ensure timely updates to both features and bug fixes, ultimately benefiting users with a more stable and feature-rich application.

Report On: Fetch commits



Repo Commits Analysis

Development Team and Recent Activity

Team Members

  • Isaac

  • Ilya Laktyushin (laktyushin)

  • Mike (overtake)

Recent Activity Summary

Isaac

  • Total Commits: 41
  • Recent Contributions:
    • Implemented various features related to star reactions, including improvements and adjustments to the UI components.
    • Fixed bugs related to the reaction search bar and audio recording.
    • Merged multiple branches, indicating collaboration on features like star subscriptions and reactions.
    • Notable changes include adding star background effects and adjusting star sizes.

Ilya Laktyushin (laktyushin)

  • Total Commits: 56
  • Recent Contributions:
    • Focused on various improvements across the application, particularly in the browser UI and star functionalities.
    • Worked extensively on localization updates, API changes, and bug fixes.
    • Collaborated with Isaac on merging branches, especially concerning star subscriptions and reactions.
    • Significant contributions include enhancements to the chat interface and various UI components.

Mike (overtake)

  • Total Commits: 7
  • Recent Contributions:
    • Primarily focused on backend improvements related to payments and subscriptions.
    • Made adjustments to the Telegram engine for handling stars and subscription features.
    • Collaborated with Ilya on several merges, indicating involvement in ongoing feature development.

Patterns, Themes, and Conclusions

  • Collaboration: There is a strong collaborative effort between Isaac and Ilya, as evidenced by numerous merge commits where they integrate each other's work. Mike also contributes but has fewer commits, indicating a more focused role in specific areas.

  • Feature Focus: The recent activity heavily revolves around enhancing star functionalities, which suggests a strategic push towards improving user engagement features within the app. This includes UI improvements and backend support for new features.

  • Bug Fixes and Improvements: A significant portion of commits is dedicated to bug fixes, indicating an ongoing commitment to maintaining code quality alongside feature development.

  • Localization Efforts: Continuous updates to localization files reflect an emphasis on internationalization, ensuring that the app remains accessible to a global audience.

Overall, the team demonstrates a balanced approach between developing new features and addressing existing issues, contributing to the project's overall health and user experience.