fix(iflow): handle null data for cookie auth on new accounts

[MasuRii]

Summary

When a new iFlow account (that hasn't completed OAuth) uses cookie-based authentication, the API returns null data because no API key exists yet. This PR adds explicit null data detection and a custom exception with actionable guidance for users.

Changes

• Add explicit null data detection in _fetch_api_key_info_with_cookie() before accessing response fields
• Create IFlowNoAPIKeyError custom exception with clear instructions for resolution
• Provide two remediation paths: OAuth authentication (auto-creates API key) or manual creation at platform.iflow.cn

Files Changed

File	Type	Impact
src/rotator_library/error_handler.py	Modified	Added IFlowNoAPIKeyError exception class with actionable message
src/rotator_library/providers/iflow_auth_base.py	Modified	Added null data check and import for new exception

Testing Instructions

1. Configure a new iFlow account (without an API key) using cookie-based authentication
2. Attempt to use the proxy - should receive a clear IFlowNoAPIKeyError with instructions instead of an opaque failure
3. Verify existing accounts with valid API keys continue to work without changes

---

Important

Adds IFlowNoAPIKeyError to handle null data in cookie-based authentication for new iFlow accounts, providing user guidance.

• Behavior:
  • Adds null data detection in _fetch_api_key_info_with_cookie() in iflow_auth_base.py to handle cases where no API key exists.
  • Raises IFlowNoAPIKeyError with guidance for users on how to resolve the issue.
• Exceptions:
  • Introduces IFlowNoAPIKeyError in error_handler.py with a message guiding users to set up an API key via OAuth or manually.
• Imports:
  • Adds import for IFlowNoAPIKeyError in iflow_auth_base.py.

^{This description was created by for 0c46c05. You can customize this summary. It will automatically update as commits are pushed.}

[mirrobot-agent]

Starting my review of the iFlow cookie auth fix for new accounts. This is a focused change - I'll analyze the new exception class and the null data handling logic.

[mirrobot-agent]

Overall Assessment

This is a well-crafted, focused PR that addresses a specific edge case with clear user guidance. The implementation is clean and follows existing patterns in the codebase.

Key Changes Reviewed

• New Exception Class: IFlowNoAPIKeyError is well-documented with actionable guidance for users
• Null Data Detection: Properly handles the case where new iFlow accounts haven't created an API key yet
• Error Messages: Clear instructions provide two resolution paths (OAuth or manual key creation)

Suggestions for Improvement

1. Export Consistency: Consider adding IFlowNoAPIKeyError to the public exports in core/__init__.py and core/errors.py to match the pattern used for CredentialNeedsReauthError
2. Context Enhancement: Passing account identifier information would help users with multiple credentials identify which account needs attention

Testing Considerations

• Verify the error is properly caught and displayed to users
• Ensure existing accounts with valid API keys continue working without any changes

This PR is ready to merge with or without the suggested improvements.

This review was generated by an AI assistant.