fix: Feedback report sources

[jatezzz]

• Separate device info from the main feedback message body.
• When generating a feedback report, search multiple output tabs (Build, App Logs, IDE Logs) for a stack trace to include, instead of only checking the currently active tab.
• Add a "Stack trace unavailable" message to the feedback body if no logs are found.

New email template:

Ticket

ADFA-1960

[greptile-apps]

Greptile Overview

Greptile Summary

Improved feedback report generation by searching across multiple output tabs (Build, App Logs, IDE Logs) for stack traces, rather than only checking the currently active tab.

Key Changes:

• Refactored getLogContent() to iterate through candidate tabs and return the first non-empty log content
• Separated device information (app version, Android version, device model) from the main feedback message body for better email formatting
• Added fallback "Stack trace unavailable" message when no logs are found in any tab

Implementation Details:
The new approach builds a list of candidate tabs starting with the current tab, then checking Build Output, Application Logs, and IDE Logs in that order. This ensures users can capture relevant error information even when they're not viewing the correct output tab when triggering feedback.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes are straightforward and well-implemented. The logic correctly iterates through candidate tabs with proper null safety checks and early returns. String resource changes are consistent with the code modifications. No custom rules are violated, and the improvements enhance UX by making stack trace collection more reliable.
• No files require special attention

Important Files Changed

File Analysis

Filename	Score	Overview
app/src/main/java/com/itsaky/androidide/activities/editor/BaseEditorActivity.kt	5/5	Refactored getLogContent() to search multiple output tabs (Build, App Logs, IDE Logs) for stack traces instead of only checking the current tab
common/src/main/java/com/itsaky/androidide/utils/FeedbackManager.kt	5/5	Separated device info from feedback message body; added fallback message when stack trace is unavailable
resources/src/main/res/values/strings.xml	5/5	Restructured feedback strings to separate device info and added new "stack trace unavailable" message

Sequence Diagram

sequenceDiagram
    participant User
    participant FAB as Feedback FAB
    participant FBM as FeedbackButtonManager
    participant BEA as BaseEditorActivity
    participant BSP as BottomSheetPager
    participant SOF as ShareableOutputFragment
    participant FM as FeedbackManager

    User->>FAB: Click feedback button
    FAB->>FBM: onClick()
    FBM->>FBM: performFeedbackAction()
    FBM->>BEA: getLogContent()
    
    BEA->>BEA: Build candidate tabs list<br/>(current, Build, App Logs, IDE Logs)
    
    loop For each tab in candidateTabs
        BEA->>BSP: getFragmentAtIndex(tabIndex)
        BSP-->>BEA: Fragment or null
        
        alt Fragment is ShareableOutputFragment
            BEA->>SOF: getShareableContent()
            SOF-->>BEA: Log content string
            
            alt Log content is not empty
                BEA-->>FBM: Return log content
            end
        end
    end
    
    alt No logs found
        BEA-->>FBM: Return null
    end
    
    FBM->>FM: showFeedbackDialog(activity, logContent)
    
    FM->>FM: Build feedback body
    alt logContent is null or empty
        FM->>FM: Use "Stack trace unavailable" message
    else logContent exists
        FM->>FM: Include log content as stack trace
    end
    
    FM->>FM: Append device info<br/>(version, Android version, device model)
    FM->>User: Show email intent with feedback

Loading

_{3 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}